1. Home
    2. Prisma
    3. Prisma Access
    4. Prisma Access (Cloud Management)
    5. Third-Party Integrations with Prisma Access
    6. Microsoft Integrations with Prisma Access
    7. Azure AD User Group Mapping in Prisma Access
    8. Add Azure Active Directory

    Add Azure Active Directory

    Add an Azure Active Directory (Azure AD) in the Cloud Identity Engine to allow the Cloud Identity Engine to collect data from your Azure AD for policy enforcement and user visibility.
    Before you begin, set up your Azure Active Directory in your Microsoft Azure account.
    To add an Azure AD in the Cloud Identity Engine, you must have at least the following role privileges in Azure AD: Application Administrator and Cloud Application Administrator. For more information about roles in Azure AD, refer to the following link. You must have an administrative account for the directory to grant the following required permissions.
    • Access Azure Service Management
    • View your basic profile
    • Maintain access to data for which you have given it access
    • Read directory data
    • View your email address
    1. From Prisma Access, open the Cloud Identity Engine app associated with your tenant.
      1. Go to
        Prisma Access
        Tenants and Services
        Cloud Identity Engine
        .
    2. In the Cloud Identity Engine app, select
      Directories
      Add New Directory
      .
    3. Set Up
       a
      Cloud Directory
      , and select
      Azure
      .
    4. Sync your directory with Azure AD.
      1. Connect to Azure AD using the authentication code flow or the client credential flow.
        This example uses the authentication code to log in to Azure AD. Using the client credential flow requires you to configure your Azure AD with necessary permissions, so ensure you have completed all of the pre-deployment steps necessary to Deploy Client Credential Flow for Azure Active Directory.
      2. Sign in with Azure
        .
      3. Enter credentials to sign in,
        Consent on behalf of your organization
         to grant the permissions that the Cloud Identity Engine requires to get the metadata with the list of directories and
        Accept
         to confirm.
      4. Test Connection
         to confirm that the Cloud Identity Engine instance can successfully communicate with the Azure directory.
        The Cloud Identity Engine checks for the primary directory. While the test is in progress, the button displays
        Testing
        . When the Cloud Identity Engine verifies the connection, the button displays
        Success
         and lists the domain name and ID for the directory. If the connection is not successful, the button displays
        Failed
         and a red exclamation point. If this occurs, confirm you have entered your Azure credentials correctly. If you have more than one directory in your Azure AD, select the radio button for each directory and
        Test Connection
        .
        Submit
         each directory individually.
      5. Customize Directory Name
         to enter a different name for the directory.
        If you are collecting data for the same domain from both an on-premises Active Directory (AD) and an Azure AD, Palo Alto Networks recommends that you create a separate Cloud Identity Engine instance for each directory type. If you must use the same Cloud Identity Engine instance and want to collect data from both an on-premises AD and an Azure AD, you must customize the directory name for the Azure AD (for example, by adding .aad to Customize Directory Name) then Reconnect Azure Active Directory. Any applications that you associate with the Cloud Identity Engine use the custom directory name.
        • The custom directory name is the alias for your Azure AD in your Cloud Identity Engine instance; it does not change the name on your directory. If you do not enter a custom directory name, the Cloud Identity Engine uses the default domain name.
        • The Cloud Identity Engine supports lowercase alphanumeric characters, periods (.), hyphens (-), and underscores (_).
        • If you associate the Cloud Identity Engine with Cortex XDR, the customized directory name must be identical to the
          Domain
           you select in Cortex XDR.
          The custom directory name must match the corresponding directory name in any app that you associate with the Cloud Identity Engine. For example, if you are using the Cloud Identity Engine with Cortex XDR, the custom directory name in the Cloud Identity Engine must be the same as the directory name in Cortex XDR.
    5. Submit
       the configuration changes.
      When you submit the configuration, the Cloud Identity Engine connects to your Azure AD and begins synchronizing attributes. The
      Sync Status
       column displays
      In Progress
       while the Cloud Identity Engine collects the attributes.

    Recommended For You

    Recommended Videos

    Recommended videos not found.

    © 2023 Palo Alto Networks, Inc. All rights reserved.

    Techdocs Logo