Skip to main content

Managed Entra

Identities Without an HR Record

Guests, admin accounts, Enterprise Apps and agents have the same access as any employee, but no contract, no offboarding and often no accountable owner. They stay until someone finds them. The Entra Health Check shows you in minutes how many are in your tenant.

480Employees with HR Records17Agents41Enterprise Apps61Admin and Shared Accounts380Guests and Partners

Closed Doesn't Mean Done

The 2023 campaign was a success, and the file has been closed since 2024. Nobody told the tenant. The agency's 40 guests keep signing in, the app belonging to the developer who left in 2025 keeps reading mailboxes with a secret that never expires, and since November the business units have been creating agents because Microsoft allows any user to do so. Nobody did anything wrong — nobody just decided what happens after the project ends. Access like this rarely surfaces during a cleanup; it surfaces when an agency employee falls for a fake sign-in page in 2027 and their guest account still opens the old Teams files.

What applies in your tenant when nobody does anything

Four settings that Microsoft turns on in every tenant. None of them are wrong. Each one is a decision that nobody at your organization made. Turn them off and see what applies instead.

  1. Any employee can invite guests

    All members can invite external users to the tenant. No justification or sponsor required.

  2. Guest accounts never expire on their own

    A guest account persists until someone deletes it. After two years, nobody usually remembers who sent the invitation.

  3. Anyone can grant apps access to their mailbox

    Users can grant permissions to third-party apps as long as no admin consent is required. Attacks like ConsentFix target exactly this.

  4. Anyone can create agent identities

    Since November 4, 2026, all users can create Agent Identity Blueprints. By the end of November, this applies to every tenant.

Lifecycle, Not Cleanup

A one-time cleanup buys you six months. What lasts is a defined lifecycle for every identity without an HR record: an accountable owner, an expiry date, a regular review. It's already running for guests; Enterprise Apps and Agent Identities follow the same logic.

Agents

Agents Have No HR Record Either

An agent has no device that Intune checks and no location that a firewall knows. What governs it is solely its identity in Entra: who is accountable for it, what it's allowed to access and when that ends. The lifecycle above therefore applies to agents just as it does to guests, with one difference: before an agent can get a sponsor, permissions and an expiry date, someone has to know it exists. In the first inventory of a tenant with 3,000 users, we found 280 agents, and 170 of them couldn't be traced to anyone in the organization. The Agent 365 Workshop therefore starts with the inventory: which agents are running, who built them, what they can access. From that comes a risk picture and a roadmap with one accountable owner per action item. What lands in Entra afterward is the same lifecycle, written as code and operated by us.

Go to the Agent 365 Workshop

We Were Ahead of the Microsoft Default

The yellow block is our lead: since October 23, the setting has been turned off in every Managed Entra tenant. Only admins and the Agent ID Developer role can create blueprints there; existing ones remain in place. Our Identity Community had assessed the announcement one day after Microsoft made it.

since 10/13/2026Microsoft announcesAny user may create blueprintssince 10/23/2026Off for our customersWorkplace Foundation v3.24.7since 11/04/2026Rollout beginsMicrosoft activates the defaultfrom 11/30/2026Active everywhereWhere nobody made a decision, everyone has permissiontoday
Entra Health Check
  • Sign-in and Conditional Access
  • Guests, apps, and agents
  • Password protection and Identity Protection
  • Privileged roles
  • read-only
  • in the browser
  • 63 checks
  • a few minutes
  • free
Start Entra Health CheckSign in with a read-permitted account. No installation, no agent.

Know where your tenant stands in minutes

The Entra Health Check reads your tenant in a matter of minutes, read-only, in the browser*. Four areas, a rating for each, and the one number that matters: who signs in how, how many guests, apps, and agents have access, and whether passwords and privileged roles are protected.

The analysis runs in your browser. Names stay with you, and you decide whether the report comes to us.

What Happens Next

Four steps. The first takes minutes and needs no appointment.
  • Run the Health Check
    Run the Health Check
    You check your own tenant, read-only, in the browser. Guests, apps and agents are counted; the names stay with you.
  • Send the report
    Send the report
    Send us the report using the form below, or book a meeting directly. Or keep it to yourself — that's a result too.
  • See the comparison
    See the comparison
    We put your report alongside our blueprint and show you in 30 minutes where the lifecycle is missing and what closes the gap.
  • Get a proposal
    Get a proposal
    Kickstarter at a fixed price, Workplace Foundation as code, Managed Entra as ongoing operations with a base fee and user fee. For agent topics, the Agent 365 Workshop — with Microsoft funding where it applies.

A Conversation with the Workplace Team

A quick check or a full consultation, fifteen or thirty minutes in Microsoft Teams with the colleagues who run Entra and Intune for our customers. Pick a duration, tell us what it's about and when works for you, and we'll send the invite.

30 minutes in Microsoft Teams

What it's about

Header image of the post Who Built These Agents

Who Built These Agents?

Andreas Hötzinger writes in the blog about what E7 and Agent 365 include, why a license doesn't clean up a tenant, and what the inventory looked like in a tenant with 3,000 users: 280 agents, 170 of them with no accountable owner. He also covers what an agent needs in Entra before it gets access, and who is ultimately responsible for it.

Entra and Intune as code, from one repository, by one team

On every sign-in, Conditional Access checks whether the device is compliant, and the answer comes from Intune. When either side is managed through the portal, you end up with rules nobody can audit. We run both as code: every policy, every compliance requirement, and every exception lives in a repository, goes through a plan and an approval, and is deployed as a release, in Entra and in Intune alike. Behind that is a team that runs Conditional Access, Passkeys, PIM, Autopilot, and device compliance for customers every day, with a Technical Account Manager who knows your tenant. Managed Entra covers identity, Managed Intune covers devices, and together they cover the whole workplace.

Questions That Come Up in the First Conversation

Answer first, reasoning after.

Can our employees still invite guests?

Yes. We recommend keeping invitations open and governing the lifecycle behind them. A ban reduces visibility more reliably than it reduces risk — files just move into private shares instead. With a sponsor, a review at 180 days and deletion at 365 days, inviting stays simple and accounts don't last forever.

What about guests who genuinely need to stay long-term?

They stay as long as their sponsor confirms them. The 180-day review is a question to someone who knows the guest, not a deletion. The account only expires after 365 days if nobody confirms it. Service providers with ongoing contracts have no issue with this; orphaned accounts do.

We have hundreds of App Registrations. Where do we start?

With three questions: which apps no longer have an active owner, which have secrets older than twelve months, and which are allowed to read all mailboxes or all files? These three lists are usually short enough to work through in an afternoon and significant enough to get leadership's attention. The Health Check gives you the first count.

Should we turn off agent creation for users?

Yes, until rules are in place. When the setting is off, only admins and the Agent ID Developer role can create blueprints; existing blueprints remain in place. For our customers, the setting has been off since Workplace Foundation v3.24.7. The next question is how business units should be allowed to build agents — and that's what the Agent 365 Workshop addresses.

We bought E7. Isn't that enough?

E7 pays for the technology, not the operations. You've licensed ID Governance, Agent 365 and the Entra Suite, and someone now has to set them up, keep them running and respond to Microsoft changes. That's exactly what Managed Entra is: turning the license into a state that holds.

What does Managed Entra cost?

A base fee per month plus a user fee per user. The starting point is the Kickstarter Workshop at a fixed price, followed by the Hosted Setup in two to four weeks. We discuss the numbers in a conversation because they depend on user count and license status. There's no surcharge per agent.

Do we need to replace our existing IAM?

No. Your existing IAM can stay — it just only knows who's in the HR system. Managed Entra takes care of the rest: guests, apps, admin accounts and agents that no IAM has ever seen. Only together do you get the full picture.

Contact us now

We are happy to help with your questions about our Managed Services.
Alexander Schlindwein
With our Managed Services, we support you in optimizing and future-proofing your IT infrastructure.
Alexander SchlindweinWorkplace Lead