Configuring Microsoft Azure Active Directory for SSO
Granting Access
- An Admin clicks this link: https://login.microsoftonline.com/organizations/adminconsent?client_id=16f9ef12-7ede-4ed6-8b4c-62fd69d474e1
The link take the organisation a user is currently logged in to and requests admin consent for the Filtered - Content Intelligence Enterprise Application. Microsoft generates the page where you can “Accept” that permissions request. For security concerns, please see Construct the URL for granting tenant-wide admin consent

- You will then be able to log into your Content Intelligence using your Microsoft AD account. If you see a 401 error page please contact our Customer Success team using: success@filtered.com
Alternative Way To Grant Access
- An admin tries to login with their standard account to app.filtered.com/<instance>
- At most companies the user will be prompted to send an admin request for access. Send the request
- If not, SSO should already be working
- Get the request approved by an admin - review admin consent requests
- Sign in to the Azure portal as one of the registered reviewers of the admin consent workflow.
- Search for and select Azure Active Directory.
- From the navigation menu, select Enterprise applications.
- Under Activity, select Admin consent requests.
- Select My Pending tab to view and act on the pending requests.
- Search for “Filtered” to find the pending request.
- Grant permission to Filtered
To review the admin consent requests and take action:
- At this point the user should be able to click the Microsoft login button and be taken to their Filtered Instance
Troubleshooting
Prerequisites
Granting tenant-wide admin consent requires you to sign in as a user that is authorized to consent on behalf of the organization. Typically an admin, if this isn’t you then it will be someone who manages your organisations Active Directory team.
To grant tenant-wide admin consent, you need:
- An Azure AD user account with one of the following roles:
- Global Administrator or Privileged Role Administrator, for granting consent for apps requesting any permission, for any API.
- Cloud Application Administrator or Application Administrator, for granting consent for apps requesting any permission for any API, except Azure AD Graph or Microsoft Graph app roles (application permissions).
- A custom directory role that includes the permission to grant permissions to applications, for the permissions required by the application.
Enterprise Application details
The Application ID and Object ID must match what is shown in your Azure Active Directory Portal if they don’t you have likely created a new application and granted permissions to it instead of to Filtered’s Content Intelligence.
Name
Filtered Technologies Limited
Tenant ID
64521441-02ae-4618-8e20-0329cd552e19
Primary domain
Application (client) ID
16f9ef12-7ede-4ed6-8b4c-62fd69d474e1
Object ID
6ce3f9e7-a457-4101-8f8c-c18412b0d915