الملاحظات تحرير

Use the Discovery Service with the SDK Assemblies

  • مقالة
  • قراءة خلال 2 دقائق

Important

Effective March 2, 2020, the regional Discovery Service will be deprecated.

For information on how to transition to use the global Discovery Service, see Modify your code to use global Discovery Service.

You can create a client for a specific Microsoft Dataverse environment and not provide the user any options about which environment they can connect with. Only valid users for that specific environment can use your client.

If you want people using your client to be able to connect to any Dataverse environment they have access to you could prompt them to enter the URL for their environment, but this is not recommended. Each user may have access to multiple Dataverse environments. Users may not know or remember the URL for their environment. Expecting people to enter this URL is bound to frustrate users.

Instead, your client should provide a list of each of the available environments based on the user’s credentials. If there is more than one environment available, your application should prompt the user to choose which environment they want to connect with.

With Dataverse, server and organization allocation may change as part of datacenter management and load balancing. Therefore, a discovery service provides a way to discover which server is serving an instance at a given time.

Global Discovery Service Endpoints:

Location Global Discovery Web service URL
Commercial https://disco.crm.dynamics.com/XRMServices/2011/Discovery.svc
North America 2 (GCC) https://globaldisco.crm9.dynamics.com
US Government L5 (DOD) https://globaldisco.crm.appsplatform.us
US Government L4 (USG) https://globaldisco.crm.microsoftdynamics.us
China operated by 21Vianet https://globaldisco.crm.dynamics.cn

See also

Global Discovery Service Sample
Discover the URL for your organization