An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
For collaboration or partnership around an execution-control architecture for AI agents in the context of Microsoft Agent 365, the appropriate paths are:
- Frontier preview / product team channels
- Agent 365 is currently available only through the Frontier preview program. Organizations in this program have direct channels to the product group. The right contact is typically the Microsoft account team and the Frontier/Agent 365 product managers they connect to. Use those existing Frontier preview engagement channels to present the architecture.
- Microsoft account team (enterprise customers)
- For enterprises, the primary route is the assigned Microsoft account team (Account Executive / Customer Success / Cloud Solution Architect). They can route the proposal to:
- Agent 365 product group
- Azure AI / Foundry team
- Security and identity teams (Entra, Defender, Purview) that integrate with Agent 365
- For enterprises, the primary route is the assigned Microsoft account team (Account Executive / Customer Success / Cloud Solution Architect). They can route the proposal to:
- Official feedback and extensibility channels
- For technical integration and extensibility, align the proposal with:
- Agent 365 SDK and agent developer guidance: https://learn.microsoft.com/microsoft-agent-365/developer/
- Governance and security for AI agents across the organization (Cloud Adoption Framework) to show how the architecture fits into existing governance patterns.
- Use those documentation channels and associated “Feedback” mechanisms to reach the engineering and documentation owners.
- For technical integration and extensibility, align the proposal with:
- Security and governance stakeholders
- Because Agent 365 is positioned as the unified control plane for observing, governing, and securing agents (with Entra Agent ID, Defender, and Purview), the most relevant Microsoft stakeholders are:
- Microsoft Agent 365 product team (control plane and registry)
- Microsoft Entra Agent ID / Agent Registry team
- Microsoft security for AI / Agent 365 security team
- These are reached indirectly via the account team or Frontier preview contacts, not by a single public individual.
- Because Agent 365 is positioned as the unified control plane for observing, governing, and securing agents (with Entra Agent ID, Defender, and Purview), the most relevant Microsoft stakeholders are:
In practice, the next step is to work through the organization’s Microsoft account representative or Frontier preview contact, describe the execution-control architecture in terms of how it enhances Agent 365’s governance, observability, and access control, and request a technical deep-dive with the Agent 365 product group.
References:
- Secure AI agents at scale using Microsoft Agent 365
- Microsoft security infrastructure extended to AI agents
- Microsoft Agent 365 SDK Overview
- Overview of Microsoft Agent 365
- Responsible AI FAQ for Microsoft Agent 365
- Governance and security for AI agents across the organization
- Agent Registry convergence with Microsoft Agent 365
- How do I get a live person at Microsoft.? - Microsoft Q&A
- I need to talk to someone!! - Microsoft Q&A