Can Agent 365–registered 3rd-party agents be invoked outside MS 365 clients and still track usage?
Hello, The documentation describes how to register a third-party agent with the Microsoft Agent 365 platform (for example an agent hosted on Google Cloud Run) in order to benefit from capabilities such as observability, governance, security, and centralized management. Does this mean that users must access these agents through Microsoft 365 entry points (such as Copilot Chat, Teams, or other Microsoft clients) in order for those capabilities to apply? Or can the same registered agent also be invoked and interacted with from third-party clients or external services (for example applications running in GCP) while still benefiting from Agent 365 features like observability, governance and/or security? What if third party agent is registered to Agent 365, but it doesn't use EntraID? It's what observability, governance and/or security will be available then? Thank you.
Ownerless, Risky and Unmanaged agents aren't reflecting in Agent 365 in admin center
1. Ownerless, Risky, and Unmanaged agents are not appearing in Agent 365 Admin Center despite having the required Agent 365 license and appropriate administrative roles. Several agents have no active owner, and I even hard deleted the owner account to simulate an ownerless scenario, but the agents are still not being identified as ownerless. 2. Risky agent classification is also not working as expected. Conditional Access and Microsoft Purview policies have been configured, and the agents have performed activities that should trigger risk indicators, yet no agents are being categorized as risky in Agent 365. 3. All Microsoft-native agents, including Copilot Studio agents, Foundry agents, and Microsoft Copilot agents, are consistently displayed as Managed. Only externally connected agents are shown as Unmanaged. If external agents are correctly identified as unmanaged, why are Microsoft-native agents not being classified as unmanaged when they meet similar conditions? Please let me know the solution to overcome this issue, Do I need to enable something which I missed or I lack permission.Agent 365 adoption resources now available
We've created a Getting Started Guide for Agent 365! You can find it on our new Agent 365 Adoption Resources page, as well as links to articles for getting started with Agent 365 in Microsoft 365 Admin Center, Microsoft Defender, Entra, and Purview. Would love to hear what you think -- or what we've missed! Please leave a comment on this post. Thank you! -- Nichole Microsoft Agent 365 – Microsoft AdoptionTues, May 12: Live AMA with Agent 365 Product Team
How to Participate Register/RSVP/Add to Cal at: Live AMA: Microsoft Agent 365 | Microsoft Community Hub Visit the AMA page on Tuesday, May 12 at 9am Pacific time to join the conversation. You can post your questions in the comments, and product team members will respond live during the AMA. Live AMA: Microsoft Agent 365 | Microsoft Community Hub
Could Agent 365 end up being just central observability platform without needing per user licenses?
Since Agent 365 allows bringing in both first-party and third-party agents, I’m curious about the identity and licensing model. If an agent is not using an Entra Agent Identity, will it still appear in Agent 365 observability or governance? In other words, could organizations use Agent 365 mainly for central visibility, monitoring, and governance of agents, even if those agents don’t have their own identities? And if that’s the case, does it mean companies could avoid needing a per-user Agent 365 license for every employee interacting with the agent? In summary if a company doesn't need OBO features, just central visibility, can they still benefit from Agent 365?OBO Agents vs. Execute-as-User Agents: What Will Agent 365 provide?
It was mentioned during the AMA session that agents from the Microsoft ecosystem (Copilot Studio, Foundry, SharePoint) will be automatically onboarded into Agent 365. However, today many of these agents execute as users, and some may continue to operate this way indefinitely. In other words, they may never receive their own Entra ID agent identity and may never run using an On-Behalf-Of (OBO) model. This raises an important question around observability, governance, and security. If these agents do not have their own identity and continue to execute under user credentials, what capabilities will Agent 365 provide for them in terms of monitoring, governance, and security controls? TL;DR: It is still unclear what observability and governance features will be available for non-OBO agents - both within Agent 365 itself and through standard platform administration tools. A clear comparison between OBO agents and non-OBO agents in terms of visibility, governance, and security capabilities would be extremely helpful. Thank youAgent 365 - can it be used just as a Governance platform for non-OBO agents?
It was mentioned that Agent 365 will allow to combine first-party, partner and third-party agents. Does this mean organizations could use the platform mainly for central visibility and governance of agents, but not necessarily for agent identities, effectively avoiding the need to pay a per-user license for everyone interacting with the agent?Live AMA: Microsoft Agent 365
Learn more about the capabilities of Agent 365 in this live 'Ask Microsoft Anything' with product and engineering team experts! Get your questions answered about capabilities for agent observability, security, and governance, developer resources, and how to get started as you confidently scale agents in your organization. How to Participate Register for the Microsoft Tech Community using your email if you haven’t already. This allows you to post comments and ask questions. Visit this page during its scheduled time to join the conversation. You can post your questions in the comments, and product team members will respond live during the AMA. Watch the session live or catch the recording on demand after the event. Keep the conversation going in the Agent 365 discussion space after the sessions conclude. It’s a great place to follow up, share what’s working, and connect with others exploring similar topics. Hope to see you there! Come ready to learn and ask our experts all of your burning questions!Partner Question on Agent 365
We are an ISV, and build solutions that are deployed on a Customers Azure Tenant. We are also in the marketplace. If we decide to make our solution "Agent 365 Enabled" (don't have a better word for it now), here are a few questions: 1. Will there be a special designation on the Microsoft Marketplace? 2. Will that incur additional ACR costs to my customer? 3. If customer decides not to have this observability turned on, do I need to control it in my packaged infrastructure deployment to toggle Yes/No? Thanks!
