This article explains how to configure the Microsoft Entra ID (formerly Azure AD) connector to integrate data about Entra ID sign-ins with Cato events and the Cloud Activities Dashboard.
Note:
Microsoft recently changed the name of Azure AD to Entra ID. All mentions of Azure AD in Cato documentation refer to Entra ID.
Overview of the Microsoft Connectors
To configure Cato's Microsoft Azure AD connector to fetch sign-in data, first you need to configure the Microsoft 365 connector as the parent app to give read permissions for the Azure AD connector. The parent app only has permissions to manage the Microsoft connectors. After configuring the Microsoft 365 connector, you can configure an Azure AD connector to retrieve the sign-in data.
If you want to import sign-in data from different sub-organizations within your organization, create a separate Microsoft 365 connector for each relevant Azure tenant, and then configure an Azure ID connector for each tenant.
Prerequisites
A Microsoft 365 E3 license or better, or a standalone Entra ID P1 or P2 plan is required.
The Microsoft 365 connector requires an admin with the global admin role to give permissions to Cato's Azure AD connector.
Required Permissions for the Microsoft Azure AD Connector
To let the Azure AD connector retrieve the sign-in data for your account, the connector gives Cato the following permissions and actions with Microsoft 365:
Connect to the Microsoft APIs and read all Microsoft Azure AD (Entra ID) data for an organization.
Sign in and read user profile.
Configuring the Microsoft Connectors
To configure the Entra ID integration, you need to:
Create the MS Tenant Integration (if you do not have this already configured)
Create the API connector in the CMA
Step 1: Configuring the MS Tenant Integration
First, configure the MS Tenant integration as the parent connector. This connector can be used for all Microsoft integrations. If you have already created the parent connector, go to step 2.
To create the Microsoft 365 parent connector:
From the navigation menu, select Resources > Integrations and click the Integrated Apps tab.
Click New. The New Connector panel opens.
In the New Connector panel, select the Microsoft 365 (New Tenant) app.

Enter the Connector Name.
Click Authorize and Save.
A new browser tab opens to the Microsoft 365 app.
In the new browser tab, authenticate to the Microsoft 365 app:
Select the Microsoft account for the Microsoft 365 app.
Enter the password for the app and approve it.
Accept the permissions to let Cato access the Microsoft 365 app.
The screen shows that you have successfully applied the permissions for the app.

You can close the browser tab and return to the Cato Management Application.
The Microsoft 365 SaaS application is added to the Integrated Apps tab.

Step 2: Configuring the Entra ID Connector
After you have created the MS Tenant integration, you can create the Entra ID connector.
Note:
When you create an API connector for a Microsoft 365 app, the connector creates an authentication certificate that is valid for 3 months, and renews the certificate 7 days before expiration.
To configure the Microsoft Azure AD connector:
From the navigation menu, select Resources > Integrations and click the Integrated Apps tab.
Click New. The New Connector panel opens.
From the Saas Application drop-down menu, select Microsoft Entra ID.
.png?sv=2026-02-06&spr=https&st=2026-09-02T11%3A52%3A57Z&se=2026-09-02T12%3A05%3A57Z&sr=c&sp=r&sig=Omim3%2FW25brFnUW6L44F6tw3qCjWs1tYcoybHCD33us%3D)
Select Sign In Activities.
In the Auth drop-down, choose Consent Microsoft
Add a Name and Description for the connector.
In the Parent ID drop-down, select the Microsoft Primary Tenant that was created in Step 1.
Click Save.
The CMA connects to the vendor
Click Authorize.
A Microsoft permissions screen will appear.
Review the requested permissions and click Accept.
The app is visible on the Integrated Apps table with a Connected status.
Understanding the Connector Status
The Status column on the Connectors Settings page shows the status of the connection between the Microsoft app and your Cato account. These are the explanations of the statuses:
Connected - Your account is connected to the app and it is working correctly.
Pending user consent - Permissions have not been granted to let Cato access the Microsoft 365 app. To resolve this issue, refresh the browser. If Status changes to Connected, the issue is resolved, if Status doesn't change, delete and recreate the connector.
Error - There is a connectivity, permissions, or other issue with the Microsoft connector. Delete and recreate the connector.
Cato Event and API Fields for Azure AD Sign-Ins
These are the relevant fields for Azure AD sign-in events of sub-type Application Sign-in.
The eventsFeed query of the Cato API shows data for Azure AD sign-ins in these fields for eventFieldName type, you can see descriptions of the fields: here.
API enum Value | Event Field |
|---|---|
is_compliant | Is Compliant |
is_managed | Is Managed |
vendor_event_id | Vendor Event Id |
tenant_id | Tenant Id |
tenant_name | Tenant Name |
sign_in_event_types | Sign In Types |
risk_level | Risk Level |
client_class | Client Class |