Microsoft Entra
Control who gets in with Entra ID, person or agent.
At every sign-in, Entra ID checks account, device and risk, and every agent gets its own identity with an accountable person. We introduce the rules step by step.
For IT teams who want to tighten sign-in, admin rights and guest access and give their first agents an identity of their own.
- Microsoft Entra ID
- Conditional Access
- Passkeys
- Privileged Identity Management
- Entra Agent ID
- ID Governance

People, guests, services, agents
A new employee gets her account on her first day, signs in with a passkey and sees exactly the applications of her role; her access ends with her last working day. The same rules apply to guests, service accounts and AI agents from Copilot Studio, Microsoft Foundry or your own applications. How we run Zero Trust as a project is described under Zero Trust & Identity Security.
Accounts, sign-in, roles
We set up accounts, sign-in, roles and policies with your IT, starting with the accounts that hold the most rights, and document every exception. The building blocks for people and agents:
- LifecycleAccounts from the HR system or on-premises AD, groups by role, access packages with an expiry date and regular reviews by managers.Result: joining, changing role and leaving adjust rights automatically.
- Passkeys and MFAPasskey profiles per group, device-bound passkeys for administrators, synced passkeys for everyone else, registration right at sign-in.Result: most sign-ins run without a password and withstand phishing.
- Conditional AccessPolicies by account, device, location and risk, first in report-only mode, then with a pilot group.Result: the sign-in log shows for every denied sign-in which policy applied.
- Administrator rightsSeparate admin accounts, roles through Privileged Identity Management only for a limited time and with a justification, emergency accounts with a FIDO2 key or certificate.Result: only the emergency accounts hold permanent admin rights.
- Agents with their own identityAgent ID for agents from Copilot Studio, Microsoft Foundry or other platforms, with a sponsor, a blueprint and dedicated policies for autonomous agents.Result: every agent has an accountable person, and your IT can block it with one policy.
- Guests and partnersB2B guests, access between the tenants of related companies and guest reviews per project.Result: partners work with their own account and lose access when the project ends.
Know your applications and lockout effects
We need an inventory of applications, directory connections, service and emergency accounts and the groups with critical rights. We clarify licences per building block: Conditional Access needs at least Entra ID P1, policies for agents also need Agent 365 or Microsoft 365 E7. Existing sign-in methods and the effects of a lockout are clarified before any change.
Sign-ins under test
We test permitted and denied sign-ins, role changes, guest access and employee departures, and for agents also a sign-in with elevated risk. The emergency accounts sign in during the test. Logs and documented exceptions help your operations team maintain policies and investigate problems.
Sound familiar? Tell us where you stand today.
ContactWhat's new.
As of: October 2026
- Since April 2026
Microsoft Entra Agent ID is generally available.
Agents receive their own identities, created from a blueprint and with a person as sponsor. They sign in through OAuth and reach tools through MCP and other agents through A2A. Since May 2026 the list of all agents is kept in Agent 365 in the Microsoft 365 admin center; the identities stay in Entra.
Source: Microsoft Learn: What's new in Microsoft Entra - As of October 2026
Conditional Access also applies to agents.
Which policy applies depends on the access pattern: when an agent acts on behalf of a person, that person's policies apply; an autonomous agent is covered through its agent identity or its blueprint, an agent with its own user account through that account. It requires Microsoft 365 E7 or Agent 365 with at least Entra ID P1.
Source: Microsoft Learn: Conditional Access for agents - Since March 2026
Synced passkeys and passkey profiles are generally available.
Passkeys can be used across several devices through password managers or bound to one device, and profiles set per group which kind applies. Since May 2026 registration campaigns prompt users to set up a passkey at sign-in, and a tenant can hold up to ten profiles.
Source: Microsoft Learn: What's new in Microsoft Entra
Where these rules apply.
Recurring configuration checks at BMC, sign-in and admin rights at M+P Ingenieure, client access in SharePoint at TaxPerts and shared protection rules for SAGW.

BMC Switzerland AG
BMC: Identifying changes in security configuration
View project
M+P Ingenieure AG
M+P Ingenieure: Protecting project access in the office and on site
View project
TaxPerts GmbH
Strengthening identity and client-document access at TaxPerts
View project
Schweizerische Akademie der Geistes- und Sozialwissenschaften (SAGW)
SAGW: Applying consistent access and protection rules
View projectRelated to your task
Sign-in, conditional access and admin rights as a project, from pilot group to handover.
Security operationsDetect and handle risky sign-ins and configuration drift on an ongoing basis.
AI governanceWho approves agents, what they may do and how their use stays traceable.
Agentic AIAgents with their own identity, limited sources and approval by a person.
Support & OperationsHave roles, guests, exceptions and agents reviewed regularly after handover.
What IT teams ask before new sign-in rules.
Does MFA also have to apply to emergency accounts?
Yes. For the Azure portal, the Entra, Intune and Microsoft 365 admin centers and the Azure tools, Microsoft requires MFA without exception; the latest start date that could be chosen for the tools was 1 July 2026. We set up emergency accounts with a FIDO2 key or certificate, store the keys separately and run regular test sign-ins.
Can we do away with passwords entirely?
For most sign-ins, yes. When a person has a passkey in Authenticator, in a password manager or on a security key, Entra ID picks the strongest method and no longer asks for a password. Applications with older sign-in methods still need one for now; we list them and plan their move.
How do we keep track of agents?
Every agent with Agent ID appears in the Entra admin center and has a sponsor. When that person leaves, a lifecycle workflow hands responsibility to their manager or co-sponsors. The list of all agents, including those from other platforms, is kept in Agent 365 in the Microsoft 365 admin center.
Does Conditional Access apply to every agent?
To every access for which Entra ID issues a token. When an agent calls an interface with an API key, Entra ID does not see that access. We therefore move agents to Agent ID, create a separate policy per access pattern and replace keys where the interface supports Entra sign-in.
What happens if a new policy hits the wrong people?
New policies first run in report-only mode and show whom they would have affected. They then apply to a pilot group, and emergency accounts stay excluded from policies that could lock them out. If a policy still misfires, we switch it back to report-only and review the sign-in log.
Agree on a useful next step
Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.
