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.
The Discovery service is accessed through two different APIs:
- For the OData V4 RESTful API: Discover the URL for your organization
- For the discovery API available through the 2011 (SOAP) endpoint: Use the Discovery service with the Microsoft.Xrm.Sdk.Discovery NameSpace
The regional Discovery service is deprecated. More information: Important changes (deprecations).