Sign in with Microsoft
How Microsoft sign-in treats personal and work or school accounts, who creates and owns your Entra tenant's network, and how admins grant consent.
Updated · ·By Ivan Vyshniak
Nothing on this page changes with your selection.
Continue with Microsoft on the sign-in page accepts both personal Microsoft accounts and work or school accounts from Microsoft Entra ID. For a work or school account, Peerlify also reads which Entra tenant you belong to, whether you are a guest there, your Entra administrator roles and your tenant's verified domains.
Personal Microsoft accounts
A personal account, such as an outlook.com or hotmail.com address, gets a network named after you, with you as its Owner, and never joins an organization's network automatically. Microsoft doesn't confirm to Peerlify that a personal account owns its email address, so such an account can't accept an invite sent by email; send it an invite link instead (see Invite people).
Work and school accounts
A work or school account gets its own network too, and can join its tenant's network. The tenant decides which network you join, never your email address.
- Who creates it. Only an Entra administrator of the tenant creates it, by signing in, and becomes its Owner: a Global Administrator, Application Administrator or Cloud Application Administrator.
- Who joins. Other people from the tenant join as Member once it exists, and Entra administrators who sign in later join as Admin. Before it exists, people get only their own network. If Manual user approval is on, members wait until an admin approves them (see Approve new members).
- Guests in your tenant never join it.
- A network without an Owner gets as its Owner the first Entra administrator of the tenant who signs in.
Networks from earlier Microsoft sign-ins
Peerlify used to group Microsoft accounts by email domain. Such a network becomes your tenant's network the first time someone signs in from the tenant that has verified that domain in Entra; it keeps its devices, rules, plan and members. If its Owner belongs to another tenant, they stay a Member and an Entra administrator of your tenant becomes the Owner when they sign in. The full rules are in How you get networks.
Leaving, and removing people
Removing someone from your tenant or disabling their account stops their Microsoft sign-ins, but their Peerlify membership stays until you remove them on the Members page. That removal sticks: their later sign-ins don't add them back until they accept an invite. See Remove a device or a person.
On the Enterprise plan, Entra ID can do this for you: with user and group provisioning, unassigning or disabling someone in Entra suspends them in the network within seconds, and Entra groups become groups you can use in access rules.
For Entra admins: grant consent
If your tenant doesn't let users consent to apps themselves, people see "Your organization's administrator must approve Peerlify" on the login page. An administrator grants consent once for the whole tenant:
- open
https://login.microsoftonline.com/<your-tenant-id>/adminconsent?client_id=<Peerlify client ID>and accept (Peerlify support gives you the client ID), or - go to Microsoft Entra admin center → Enterprise applications → Peerlify → Permissions → Grant admin consent for <your organization>.
Peerlify asks only for permission to read the signed-in user's basic profile (User.Read), which is also what lets it read your organization's verified domains. If your tenant lets users consent only to apps from verified publishers, and Microsoft shows Peerlify's publisher as unverified, users can't consent themselves either; an administrator grants consent as above.
If sign-in fails
See Sign-in and enrollment problems for every message the login page shows, including Your Entra admin has to approve Peerlify.
Limits
- Entra groups aren't used for roles; roles are managed on the Members page.
- Adding and removing members and syncing groups from Entra ID is a separate setup, on the Enterprise plan: see User and group provisioning.