Microsoft prerequisites checklist
What a Microsoft administrator confirms for Meridian in Teams, the Agent 365 import, Entra SSO, and Azure OpenAI or Copilot Studio cost access.
Best for: Microsoft administrators preparing a tenant for Meridian
Microsoft prerequisites checklist
10 November 2026.
Short answer. This checklist is what a Microsoft administrator confirms before Meridian in Teams, the Agent 365 import, Entra SSO, and Azure OpenAI or Copilot Studio cost access. Agent 365 import is available for a tenant with a Microsoft Agent 365 license or Microsoft 365 E7/G7. It also needs consent from an AI administrator or a Global administrator, and the pre-flight check on Settings, Microsoft Teams & Copilot. A row on Settings is marked done only when Meridian has checked it.
This page is what a Microsoft administrator confirms before Meridian in Teams, the Agent 365 import, SSO with Entra, and Azure OpenAI or Copilot Studio cost access. The same list is on Settings, Microsoft Teams & Copilot. A row there is marked done only when Meridian has checked it.
Meridian in Teams
Required: a Microsoft 365 tenant in the global cloud, and the Meridian app installed in Teams.
Who does it: a Teams administrator or a Global administrator installs the app. An organization owner or admin in Meridian connects that tenant on Settings, Microsoft Teams & Copilot.
How to verify: the settings page says the tenant is connected, and the Meridian app appears in Teams. Meridian does not check the Teams install from this page.
Agent 365 import
Required: admin consent for Meridian's registry app, with the application permissions CopilotPackages.Read.All and AgentRegistration.Read.All. The tenant also needs a Microsoft Agent 365 license or Microsoft 365 E7/G7. That license is included with Microsoft 365 E7 and G7 and is sold on its own. Other Microsoft 365 plans do not include the Graph API that reads the agent registry. The API is in the global service only.
Who does it: a Global administrator grants the admin consent. Microsoft's admin documentation also names the AI administrator or Global administrator for people using these registry APIs.
Agent 365 import is available for a tenant with a Microsoft Agent 365 license or Microsoft 365 E7/G7. How to verify: on Settings, Microsoft Teams & Copilot, choose Check again. The page says "Agent 365 available: Meridian will import your agents daily" when the catalog list succeeds. If the tenant is not licensed, the page says Agent 365 isn't available and names the license. If consent did not include a required permission, the page says consent is incomplete and names the permission. When that check is within a few minutes of approval, the page says Microsoft can take a few minutes to apply new consent. Check again stays on the page while the catalog is incomplete or unavailable, and is hidden once Agent 365 is available. Meridian imports daily only after the catalog check succeeds. A tenant that is not licensed is not raised as a daily alert.
Stop the import: an organization owner or admin chooses Stop registry import on that same page. Meridian stops the daily import for that tenant and deletes the snapshot it stored. That does not remove the app from Microsoft. To remove Microsoft's consent, in Entra open Enterprise applications and remove the registry app.
See From Agent 365 to the General Ledger.
Sources, read 9 November 2026:
- Package Management API overview, dated 27 August 2026, updated 28 September 2026. Access requires a Microsoft Agent 365 license.
- List Copilot packages, dated 27 August 2026, updated 21 October 2026. Application permission CopilotPackages.Read.All. Global service only.
- Microsoft Agent 365 service description, dated 30 September 2026, updated 1 October 2026. The Graph API requires Microsoft 365 E7, G7, or Agent 365, and is not included with other Microsoft 365 plans.
- Graph API for agent registry and agent details, dated 24 February 2026, updated 4 August 2026. These APIs require the AI administrator or Global administrator role.
SSO with Microsoft Entra
Required: a SAML application in Entra, and the company's email domain listed on the Meridian SSO configuration.
Who does it: an organization admin in Meridian opens Governance, SSO, chooses Azure AD (Entra ID), and enters the entity id, sign-in URL, and certificate. A Global administrator or Application administrator creates that SAML application in Entra and uploads Meridian's service-provider metadata.
How to verify: a person at that domain chooses Login with SSO on the sign-in page, enters their work email, and lands in the company. Password sign-in stays on the same page. Meridian does not turn password sign-in off. The settings checklist does not mark SSO done; confirm a sign-in.
The setup steps are in SSO, team, and departments.
Azure OpenAI cost access
Required: an Azure subscription that contains the Azure OpenAI resource, and permission to read its cost.
Who does it: a billing administrator assigns Cost Management Reader on that subscription, then a Meridian admin connects the subscription.
How to verify: Azure Cost Management shows cost for the Azure OpenAI resource, and the connected subscription appears in Meridian. This checklist does not mark the row done.
Copilot Studio cost access
Required: a Power Platform environment with Copilot Studio, and billing visibility for that environment's consumption.
Who does it: a Power Platform administrator confirms the environment and that a billing reader can see its consumption.
How to verify: the Power Platform admin center shows the environment and its consumption. This checklist does not mark the row done.