Forum Widgets
Latest Discussions
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.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 you
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?Agent 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?
Unified Multi-Tenant Management Console for MSPs and IT Providers
Microsoft would benefit from offering a truly unified, multi-tenant console designed for MSPs and IT support providers, enabling them to manage multiple client organisations from a single interface. This solution should support the integration of each client’s own domains, centralised administration across Microsoft 365, Azure, and Entra ID environments, granular delegation of permissions, and consolidated visibility into users, devices, licences, policies, and incidents. Such a tool would significantly reduce operational complexity, strengthen security, and address a genuine need for partners who manage multiple tenants on a daily basis.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!Agent 365 Questions
Please clarify, about Agent 365 licenses, there are lot of confusions in this space (e.g who needs license, what will be covered - 1st party, studio agents, dependency with security suite - E5, Defender cloud apps etc) Please help us to understand, how to setup Agent 365 in the organization start to end (e.g. different admin configurations in Purview, Entra, Defender, etc), also, would be cool, to have this documented in learn.microsoft link Is looks like Agent 365, another product with a new license build on existing product & configurations which exist already? (e.g. DSPM, Defender, Entra CAS, etc), if so, why another license model? What happens after 1st of May, for the orgs that did not purchase Agent 365, what will be affected? (like Agent Inventory in MAC, Template, DSPM AI, etc) will disappear?Request for Best Practices on Using Microsoft Agent 365
Hello Community, I am seeking guidance on best practices for effectively using Microsoft Agent 365. Specifically, I am interested in recommendations related to governance, security and access control, agent monitoring, and integration with Microsoft 365 services. If you have practical experience or proven approaches in these areas, your insights would be greatly appreciated. Thank you, Mohammad Shohal Bhuiyan
