A company has two development instances, two test instances, two staging instances, and one production instance. The test team reports connection issues with the test and staging instances. You need…

Question

Options

• Ahttps://myorg.api.crm.dynamics.com/api/data/v.9.1/
• Bhttps://dev.crm.dynamics.com/api/discovery/v9.1/Instances
• Chttps://dev.crm.dynamics.com/api/discovery/v9.1/Instances(UniqueName='myorg')
• Dhttps://disco.crm.dynamics.com/api/discovery/v9.1/
• Ehttps://globaldisco.crm.dynamics.com/api/discovery/v9.1/Instances

• A
  7% (4)
• B
  3% (2)
• C
  80% (47)
• D
  10% (6)

Explanation

Options C and E are correct because they use valid Discovery API endpoints that return instance access information for the authenticated user. Option E (globaldisco.crm.dynamics.com) is the Global Discovery Service endpoint, which returns all Dynamics 365/Dataverse instances the signed-in user has access to across every region - the most direct way to audit access. Option C uses the Instances(UniqueName='myorg') OData key syntax against a regional discovery endpoint, which queries for a specific named instance and returns its details only if the caller has access, making it a valid single-instance access check.

Why the distractors fail:

• A (/api/data/v9.1/) is the Web API (OData) endpoint for querying data inside a known org, not for discovering which orgs a user can reach.
• B uses dev.crm.dynamics.com, which is not a valid discovery service hostname; the regional discovery host is disco.crm.dynamics.com.
• D (disco.crm.dynamics.com/api/discovery/v9.1/) is missing the /Instances segment, so it returns the OData service document rather than the instance list.

Memory tip: Think "Global disco = global access list; UniqueName = verify one specific instance." If you see globaldisco → it lists everything you can touch; if you see Instances(UniqueName='...') → it pinpoints one org by name.

No community discussion yet for this question.