Azure, Power Platform, cost and data are not setup details for later. They decide whether the other six steps hold.
Fit the foundation to the agent. An agent that only lives in Microsoft 365 doesn't need its own Azure landing zone. An agent hosted in Azure does. Start discovery now, and check the foundations that apply before anything goes to production.
Azure: a landing zone, not a loose subscription
An Azure landing zone is a prepared environment where identity, network, policy and monitoring are already in place. The platform team runs the shared part. The workload team runs the agent.
The eight design areas to settle
- Billing and tenant. A named owner and cost centre for every subscription.
- Identity and access. Least-privilege roles, and managed identities instead of API keys.
- Network and connectivity. Known routes in and out, private endpoints and working DNS.
- Resource organisation. Management groups and subscriptions that separate platform from workload.
- Security. Controls for every part of the environment, with secrets in Key Vault.
- Management. Logs, metrics and alerts that reach a named person.
- Governance. Azure Policy enforces the rules and flags drift.
- Automation. Infrastructure as code, so test and production match.
Who runs what
Platform teamThe hub network and firewall, DNS, policies on the management group and the shared connection to everything else.
Workload teamMicrosoft Foundry, the app with its search and storage, Key Vault, workload monitoring, and its own subnets and private endpoints.
Test before go-live
Private DNS resolves. Blocked routes stay blocked. Roles grant only what is needed. Alerts reach a person.
Watch out Treat Microsoft's reference architecture as a starting point, not a shopping list. Fully deployed, its chat baseline landing zone is likely to cost more than $100 a day.
- Who
- Azure platform team and workload team
- Evidence
- Approved architecture, policy and role checks, network test results and a handover to operations
ReadIntroduction to AI landing zonesCloud Adoption Framework: govern
Power Platform: decide where makers build
Every tenant has one shared default environment, and without a plan that is where agents pile up. An environment strategy gives makers a safe place to build and gives production a controlled way in.
Get in order
- Name the admins. A Power Platform admin for the tenant, and environment admins where it matters.
- Secure the default environment. Limit sharing, restrict connectors with a data policy, and keep it for personal productivity.
- Route makers away from default. Environment routing sends each maker to their own developer environment.
- Group your environments. Development, test and production groups, each with its own rules.
- Release through pipelines. Solutions move from development to production, with an approval in between.
- Control who creates environments. Only admins create production environments, so capacity stays planned.
- Tell makers the rules. Where to build, which connectors they can use and how to ask for more.
Microsoft's common starting points
- 20people at most that one app, flow or agent is shared with in the default environment
- 5people at most in a maker's own developer environment
- Blocksolution checker in default and production. Warn in developer and sandbox.
Watch out Environment groups don't apply data policies for you, so scope each policy to the right environments yourself. A new sharing limit only affects future sharing, so check what is already shared. Groups, rules and routing need Managed Environments, and those need premium licences.
Changed this month. Dataverse for Teams environments are deprecated. You can't create new ones since 15 November 2026, so upgrade the ones you want to keep.
- Who
- Power Platform admin and environment admins
- Evidence
- Environment map, routing and group rules, a release approval and a capacity review
ReadPower Platform governance overviewEnvironment strategy
Cost: name the payer before the pilot
Plan, control, optimise. Every agent needs someone who pays for it, a forecast, and an agreed answer to one question: what happens when it reaches the limit?
Get in order
- Name the payer. A billing owner and a cost centre for every agent.
- Forecast the whole bill. Model usage, search, hosting, storage and logging in Azure. Copilot Credits and licences in Microsoft 365 and Power Platform. Charges from other providers.
- Set alerts, and limits where they exist. Know which of the two you actually have.
- Bound the agent itself. Cap retries, tool calls, loops and parallel runs.
- Decide who acts on an alert. Write it down and test it once.
Three places to manage cost, three behaviours
| Where | What it covers | At the limit | Good to know |
| Azure Cost Management | Azure charges for a management group, subscription or resource group. | Sends alerts and can trigger an action group. Nothing stops. | Cost data usually arrives 8 to 24 hours later. Budgets are checked once a day. |
| Power Platform admin centre | Copilot Studio agents, with credits and capacity per environment. | Depends on how credits are allocated and billed. As presented at Ignite, prepaid credits are capped per environment and pay-as-you-go is not. | The place for capacity allocation and detail per workload. |
| Microsoft 365 admin centre | Copilot Credits by spending policy, user, group, agent and service. | Spending policies set limits for users and groups. A task that is already running can finish past a per-user limit. | Refreshes every 2 to 4 hours. Shows an estimate that may differ from your bill. |
Two ways to fund agents
Fund a critical agent"We need to manage AskHR's costs, so users don't have to self-fund." Put the spending policy on the agent or on its environment.
Fund people to experiment"I want my makers to build, with a personal spending limit." Put the spending policy on users or groups.
Watch out An Azure budget is an alarm, not a brake. When it is reached, Azure sends alerts. Resources keep running and the bill keeps growing.
Moving cost management to the Microsoft 365 admin centre in five steps
- Assign roles. AI Administrator to set policies, AI Reader to review spend.
- Review what you have. For each environment: credits allocated, billing plan, agent limits and who owns it.
- Decide the policy type. A department's agents: an environment policy. One critical agent: a resource policy. Makers: a user or group policy.
- Pilot one environment. Set limits and alerts, and link it to the department's Azure subscription for chargeback.
- Expand. Environment by environment.
These steps were presented at Microsoft Ignite 2026 in session BRK262. Parts of it are new or still rolling out, so check what your tenant has before you plan around it.
- Who
- Finance or FinOps, platform admin and business owner
- Evidence
- A funding decision, a forecast, one tested alert and one tested limit
ReadAzure budgetsMonitor Copilot Credit spending
Data: fix access before you speed it up
An agent finds whatever its users, or its own identity, can already reach. If a salary sheet was shared too widely years ago, an agent will find it faster than any person would.
Get in order
- Fix oversharing. Find the sites and files that are shared too widely, and repair the permissions.
- Choose the sources. Decide which data an agent may use, who owns it and how fresh it must be.
- Settle the identity. Does the agent act with the user's permissions or with its own? Test what it can reach, and what it must not.
- Set guardrails. Sensitivity labels, data loss prevention, retention and audit, where your licences cover them.
- Treat the conversation as data. Prompts, answers, memory and logs: who can read them, how long are they kept, and where?
Watch out Read-only is not low-risk. An agent that only reads can still surface something sensitive. And hiding a site from Copilot buys you time. It doesn't repair the permissions.
- Who
- Data owners, the identity team, and security and compliance
- Evidence
- Oversharing fixed or accepted, an approved source list, and access tests that pass and fail as expected
ReadSecure and governed data foundationData access governance reportsOn this blog: sensitivity labels first