M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Connected organizations

Concept

Partner organizations declared in Microsoft Entra entitlement management by domain or identity provider, whose users may request specific access packages under a policy.

✦ CONCEPTConnected organizationsM365.FM
Title graphic: Connected organizations (Concept)

Also discussed

The episode about Connected organizations also covers Microsoft Entra ID Governance, Access packages, Entitlement management, Identity lifecycle management, Access reviews and Microsoft Entra Privileged Identity Management (PIM).

Description

Connected organizations are a concept in Microsoft Entra entitlement management. A connected organization is another organization with which a business relationship exists. For its users to reach resources in a directory, a representation of those users has to exist in that directory, and entitlement management can bring it in on demand. The purpose is to simplify access for groups of people from specific external organizations and to control which of them are allowed to request access packages under a given policy.

A connected organization defines its users in one of four ways. The first is another Microsoft Entra directory. The second is a non-Microsoft directory that uses SAML or WS-Fed federation. The third is a shared domain used by email addresses, where users sign in with one-time passcodes. The fourth is Microsoft accounts. A single connected organization can cover several directories and domains, so one partner with multiple tenants or domains can be represented as one entry. For domains that have no directory, email one-time passcodes must be enabled. Domain search requires the full domain name, and domains can be blocked by B2B allow or deny lists, which can affect whether a partner's users are accepted.

Each connected organization can have sponsors. Sponsors can be internal members or external guests, and they can act as contacts and approvers for requests that come from that organization. This allows approval to be handled by someone who knows the business relationship rather than by a central team alone.

Connected organizations have one of two states. A configured organization is the default when an administrator creates one manually. A proposed organization is created automatically when a requester has no matching connected organization, and it applies only to policies that target it directly. Managing connected organizations requires at least the Identity Governance Administrator role.

In practice, connected organizations are used together with access packages. A policy on an access package can be scoped so that only users from selected connected organizations may request it. When a request from such a user is approved, Microsoft invites the user into the directory so that access can be granted. Because access packages support multi-stage approval and time-limited assignments, guest access granted this way can expire and be removed automatically, which supports offboarding and lifecycle governance of external users.

The M365.FM episode "Govern Microsoft 365 Guest Access and Offboarding" (2025-11-03) places connected organizations within this broader picture of access governance. The episode describes capabilities such as controlling who can access applications and resources through multi-stage approval and time-limited assignments, granting access based on identity properties and removing it when those properties change, and letting identities from connected organizations request access, with Microsoft inviting them into the directory upon approval. It also states that guest access is removed automatically when packages expire.

Typical decisions around the concept include which partners to declare as connected organizations, whether to define them by Microsoft Entra directory, federated identity provider, domain or Microsoft account, who should act as sponsors, and which access package policies should be limited to specific organizations. Another consideration is whether B2B allow or deny lists, or the lack of email one-time passcodes, could prevent users from a partner domain from signing in.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Episodes about Connected organizations

Episodes in which Connected organizations is discussed:

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What is a connected organization in Microsoft Entra entitlement management? (AI)

It is an external organization with which a business relationship exists, declared by domain or identity provider. Its users can be allowed to request specific access packages under a policy.

How can users of a connected organization be defined? (AI)

Users can come from another Microsoft Entra directory, a non-Microsoft directory using SAML or WS-Fed federation, a shared email domain with one-time passcodes, or Microsoft accounts. One connected organization can cover several directories and domains.

What is the difference between configured and proposed connected organizations? (AI)

A configured one is the default when created manually. A proposed one is created automatically when a requester has no matching organization and applies only to policies that target it directly.

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: