Shared Signals with Microsoft Entra ID Beta
Microsoft Entra ID does not receive Shared Signals events from third-party transmitters. XFA instead revokes the user's sessions through the Microsoft Graph API. On the XFA side, Shared Signals is in beta and turned on per organization on request (see the overview).
Note: This guide assumes that you have an account set up with XFA for your organization, that you're an administrator for that organization on XFA, and that a Microsoft Entra administrator who can grant admin consent for Microsoft Graph application permissions (Global Administrator or Privileged Role Administrator) can join you for one step. If you do not have an account, you can create one at https://dashboard.xfa.tech/signup.
What happens on a non-compliant device
When a device of your organization becomes not compliant (see what "not compliant" means), XFA calls Microsoft Graph to revoke the user's sign-in sessions (revokeSignInSessions). Entra ID invalidates the user's refresh tokens and session cookies, so every application that goes back to Entra ID has to sign the user in again. When the device becomes compliant again, nothing is sent: the user simply signs in again.
Applications that are already open keep the access token they hold. How long that access lasts depends on the application. Microsoft services that support Continuous Access Evaluation, such as Exchange Online, SharePoint Online and Teams, treat the revocation as a critical event and end access in near real time, which Microsoft says can take up to 15 minutes. Other applications keep working until their access token expires; Microsoft's default access token lifetime varies and can be changed by policy.
A revoked session only keeps the device out when the next sign-in is checked by XFA. Make sure XFA is enforced as the External Authentication Method for the users you cover; otherwise the user signs back in on the same, non-compliant device.
Prerequisites
- Admin consent for the Microsoft application XFA Shared Signals in your tenant. It asks for one Microsoft Graph application permission,
User.RevokeSessions.All, which lets XFA sign users out. It grants no access to user data. You grant it during the steps below. - Your Microsoft Entra tenant is not connected to another XFA organization. A tenant can be connected to one XFA organization only.
Shared Signals has a grant of its own. You do not need a Microsoft connection under Discovery for it.
1. Add the Microsoft Entra connection in XFA
- In the XFA dashboard, open Device security > Shared Signals.
- Click Add connection.
- Enter a Name, for example
Microsoft Entra, and choose Microsoft Entra as the Receiver. - Click Continue to Microsoft.
2. Grant consent in Microsoft
- Microsoft shows its admin consent page for the application XFA Shared Signals. Sign in with a Microsoft Entra administrator account that can grant admin consent.
- Review the requested permission, sign users out (
User.RevokeSessions.All), and accept. - Microsoft then signs you in to the same tenant once more, usually without asking anything because you just signed in, and returns you to the Shared Signals page, where the connection appears.
The second sign-in is how XFA confirms that the tenant is yours to connect. It must be a Global Administrator or Privileged Role Administrator of the tenant that granted consent, the roles that can grant it; any other account of that tenant, and any guest account, is refused.
Before the connection is added, XFA asks Microsoft for a token for your tenant, so a connection only appears once Microsoft has confirmed the consent. XFA creates the connection's stream right away. There is no token to copy: XFA calls Microsoft Graph itself.
To run the consent again, for example after it was removed in Microsoft, click Grant Microsoft consent on the connection.
3. Verify
On the Shared Signals page, find the stream under your Microsoft Entra connection and click Send test event. The test signs nobody out. It checks that Microsoft issues XFA a token for your tenant and that the token carries the User.RevokeSessions.All permission. The result is shown on the stream.
Right after consent, the test can fail for a few minutes while Microsoft applies the permission. Wait and try again, or click Grant Microsoft consent on the connection again.
To see a real revocation, let a device of a test user fail a check that blocks in a policy attached to one of your applications. Within minutes the user's Entra ID sessions are revoked, and signing in again through XFA is blocked until the device is fixed. The revocation shows in your tenant's Microsoft Entra audit logs under the category UserManagement, initiated by the application XFA Shared Signals.
Troubleshooting
- "Microsoft Entra connections are not available yet. Contact XFA support to have them enabled.": contact support@xfa.tech.
- "Microsoft consent was not granted, so no connection was added.": the administrator declined or closed the consent page, and the message shows Microsoft's reason when it gives one. Ask a Microsoft Entra administrator who can grant admin consent to accept it, and add the connection again.
- "Microsoft has not confirmed the consent for this tenant yet.": Microsoft can take a moment to confirm a new consent. Wait a minute and add the connection again.
- "This Microsoft consent could not be matched to a request from this browser, so nothing was added.": finish the consent in the same browser where you clicked Continue to Microsoft, within an hour. Add the connection again.
- "XFA could not confirm that you are an administrator of this Microsoft tenant, so no connection was added.": the second sign-in used an account of another tenant, a guest account, or an account that is neither Global Administrator nor Privileged Role Administrator. Sign in to Microsoft as a Global Administrator or Privileged Role Administrator of the tenant you granted consent for and add the connection again.
- "This Microsoft tenant is already connected to another XFA organization.": a tenant can be connected to one XFA organization only. Contact support@xfa.tech if the tenant is yours.
- The test event fails with a missing permission: Microsoft may still be applying the consent. Wait a few minutes, then try again or click Grant Microsoft consent.
- The stream shows failed deliveries after it worked before: the consent may have been removed in Microsoft. Click Grant Microsoft consent on the connection.
- The user is not signed out: check that the user's email in XFA matches the user principal name in Entra ID, and that the failing check is set to block in a policy that is attached to an application. A device that merely warns sends nothing.
- An open application keeps working: the application still holds a valid access token. Applications without Continuous Access Evaluation keep access until that token expires.
- The user signs back in on the same device: sign-in for that user does not go through XFA. See the warning above.
- The user was signed out more than once: every change from compliant to not compliant revokes the sessions again, including a change the hourly re-evaluation finds. Fix the device to stop the changes.