Question 45 — AB-650 Practice Exam 4
For each Agent ID creation or integration method, drag the appropriate platform to the corresponding box in the Correct Match column.
Each item may be used once or not at all.
| Option | Correct Match |
|---|---|
| Automatically provisions a blueprint and identity for each project and creates a dedicated identity for each agent that is published | [Gap 1] |
| Can automatically assign an identity to an agent created within the platform | [Gap 2] |
| Allows developers to manage agent identity blueprints directly through the Developer Portal | [Gap 3] |
| Gives each managed agent its own Agent ID covering identity, access, and lifecycle | [Gap 4] |
| Can be configured so a hosted application connects to resources by using the agent identity platform | [Gap 5] |
| Connects externally hosted agents through the Microsoft Entra Auth SDK or workload identity federation | [Gap 6] |
- Copilot Studio
- Azure App Service or Azure Functions
- Standalone service principal deployment
- Microsoft Teams
- Microsoft Agent 365
- Third-party agent platforms
- Microsoft Foundry
Correct answers
- Gap 1: Microsoft Foundry
- Gap 2: Copilot Studio
- Gap 3: Microsoft Teams
- Gap 4: Microsoft Agent 365
- Gap 5: Azure App Service or Azure Functions
- Gap 6: Third-party agent platforms
Explanations
Correct Matches
Microsoft Foundry – Foundry can automatically establish the required blueprint and identity for a project and provide a dedicated identity for an agent when that agent is published.
Copilot Studio – Copilot Studio can automatically assign an identity to an agent built through the service.
Microsoft Teams – Teams development supports direct blueprint management through the Developer Portal.
Microsoft Agent 365 – Each managed agent receives its own Agent ID, allowing identity, access, and lifecycle governance to be established for the agent.
Azure App Service or Azure Functions – Applications hosted on these Azure services can be configured to use the agent identity platform when connecting to other resources.
Third-party agent platforms – Agents hosted on platforms such as AWS Bedrock or n8n can integrate with Microsoft Entra Agent ID through the Microsoft Entra Auth SDK or workload identity federation.
Unused Item
Standalone service principal deployment – A standalone service principal can authenticate application activity, but simply creating one does not connect a third-party or hosted agent to the purpose-built Microsoft Entra Agent ID object model.