Skip to content

Federation

Federation tells Microsoft 365 to redirect authentication for your domain to BlokSec instead of asking for a password. After federation is configured, users with email addresses on your domain (e.g., jane@yourcompany.com) will see the BlokSec sign-in page when they sign in to any Microsoft 365 application.

Before you begin, make sure:

  • You’ve completed the Application Setup step
  • You have Global Administrator access to your Microsoft Entra ID (Azure AD) tenant
  • Your domain (e.g., yourcompany.com) is verified in your Microsoft 365 tenant
  • The domain is currently set to Managed authentication (not already federated with another provider)
  1. In the BlokSec admin console, open your Microsoft 365 application
  2. In the Microsoft Integration panel, click Integrate Microsoft 365
Microsoft Integration panel on the application page, not yet connected, with an Integrate Microsoft 365 button
Start the integration from the Microsoft Integration panel

Click Connect Microsoft tenant. A Microsoft window opens where you sign in with your Microsoft Entra ID Global Administrator account and then approve BlokSec’s access for your organization. Both happen in the same window, and the window closes on its own when it’s done.

Microsoft sign-in prompt asking for Global Administrator credentials
Sign in with your Global Administrator account

After signing in, the wizard shows your verified domains. Select the domain you want to federate with BlokSec.

Domain selection showing verified domains in the Microsoft 365 tenant
Select the domain to federate

The wizard shows you exactly what will be configured:

  • Passive sign-in URI — The BlokSec endpoint where Microsoft will redirect users for authentication
  • Issuer URI — The unique identifier BlokSec uses to sign tokens
  • Metadata exchange URI — Where Microsoft retrieves BlokSec’s federation metadata
  • Sign-out URI — Where Microsoft sends users when they sign out
  • Signing certificate — The certificate used to verify BlokSec’s security tokens

The review step also carries a switch for whether BlokSec creates users in your Microsoft 365 tenant. Leave it on unless you already provision these users another way: once a domain is federated, Microsoft no longer lets you create users on it from its admin portals, so you would need the Graph API, PowerShell, or directory sync instead. See Provisioning for what it does. You can change this later in the application’s settings.

Click Apply federation to execute the configuration. The wizard makes a series of Microsoft Graph API calls to set up federation:

  1. Verifies the domain exists and is verified
  2. Checks for any existing federation configuration
  3. Creates the BlokSec federation configuration
  4. Reads back and verifies the configuration was applied correctly
Review screen showing the federation configuration that will be applied, with step-by-step Graph API calls
Review the configuration before applying

Once the wizard completes, you can verify that federation is working:

  1. Open a private/incognito browser window (to avoid cached sessions)
  2. Go to https://portal.office.com
  3. Enter an email address on your federated domain (e.g., jane@yourcompany.com)
  4. Microsoft should redirect you to the BlokSec sign-in page instead of asking for a password
BlokSec sign-in page showing after Microsoft 365 redirects for a federated domain
Users see the BlokSec sign-in page instead of a password prompt

If you need to remove federation and revert to Microsoft-managed authentication:

  1. Open your Microsoft 365 application in the BlokSec admin console
  2. In the Microsoft Integration panel, expand Federation details
  3. Click Revert

This reverts the domain to managed authentication, and users will be asked for their Microsoft password again. Federation can be re-added at any time.

The Microsoft Integration panel shows whether the domain is federated. Each time you open the application, BlokSec also checks with Microsoft that the domain is still federated: the panel reads Connected when Microsoft agrees, Reverted in Entra if the domain was changed back to managed authentication outside BlokSec (users on it are signing in with Microsoft until you re-federate, and the identity import is paused), and Connected · unverified if Microsoft could not be reached — for example before access has been granted.

  • If BlokSec cannot reach Microsoft to check, the page says so rather than guessing.