Onboarding an App Using Azure AD Credentials
Table of Contents
Expand all | Collapse all
-
-
- Allowed List of IP Addresses
-
- Begin Scanning a Bitbucket App
- Begin Scanning a Box App
- Begin Scanning ChatGPT Enterprise App
- Begin Scanning a Cisco Webex Teams App
- Begin Scanning a Confluence App
- Begin Scanning a Confluence Data Center App
- Begin Scanning a Dropbox App
- Begin Scanning a GitHub App
- Begin Scanning a Gmail App
- Begin Scanning a Google Drive App
- Begin Scanning a Jira App
- Begin Scanning a Jira Data Center App
- Begin Scanning a Microsoft Exchange App
- Begin Scanning Office 365 Apps
- Begin Scanning a Microsoft Teams App
- Begin Scanning a Salesforce App
- Begin Scanning a ServiceNow App
- Begin Scanning a ShareFile App
- Begin Scanning a Slack Enterprise App
- Begin Scanning a Slack for Pro and Business App
- Begin Scanning a Workday App (Beta)
- Begin Scanning a Zendesk App
- Begin Scanning a Zoom App
- Reauthenticate to a Cloud App
- Verify Permissions on Cloud Apps
- Start Scanning a Cloud App
- Rescan a Managed Cloud App
- Delete Cloud Apps Managed by Data Security
- API Throttling
- Configure Classification Labels
- Microsoft Labeling for Office 365
- Google Drive Labeling
- Configure Phishing Analysis
- Configure WildFire Analysis
-
-
-
- What is an Incident?
- Assess New Incidents on Data Security
- Filter Incidents
- Configure Slack Notification Alerts on Data Security
- Security Controls Incident Details
- Track Down Threats with WildFire Report
- Customize the Incident Categories
- Close Incidents
- Download Assets for Incidents
- View Asset Snippets for Incidents
- Analyze Inherited Exposure
- Email Asset Owners
- Modify Incident Status
-
-
-
- What’s SaaS Security Inline?
- Navigate To SaaS Security Inline
- SaaS Visibility for NGFW
- SaaS Visibility and Controls for NGFW
- SaaS Visibility for Prisma Access
- SaaS Visibility and Controls for Panorama Managed Prisma Access
- SaaS Visibility and Controls for Cloud Managed Prisma Access
- Activate SaaS Security Inline for NGFW
- Activate SaaS Security Inline for VM-Series Firewalls with Software NGFW Credits
- Activate SaaS Security Inline for Prisma Access
- Connect SaaS Security Inline and Strata Logging Service
- Integrate with Azure Active Directory
-
-
- SaaS Policy Rule Recommendations
- App-ID Cloud Engine
- Guidelines for SaaS Policy Rule Recommendations
- Predefined SaaS Policy Rule Recommendations
- Apply Predefined SaaS Policy Rule Recommendations
- Create SaaS Policy Rule Recommendations
- Delete SaaS Policy Rule Recommendations
- Enable SaaS Policy Rule Recommendations
- Modify Active SaaS Policy Rule Recommendations
- Monitor SaaS Policy Rule Recommendations
-
- Enable Automatic Updates for SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Import New SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Update Imported SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Remove Deleted SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Manage Enforcement of Rule Recommendations on NGFW
- Manage Enforcement of Rule Recommendations on Panorama Managed Prisma Access
- Change Risk Score for Discovered SaaS Apps
-
-
-
-
- Onboarding Overview for Supported SaaS Apps
- Onboard an Aha.io App to SSPM
- Onboard an Alteryx Designer Cloud App to SSPM
- Onboard an Aptible App to SSPM
- Onboard an ArcGIS App to SSPM
- Onboard an Articulate Global App to SSPM
- Onboard an Atlassian App to SSPM
- Onboard a BambooHR App to SSPM
- Onboard a Basecamp App to SSPM
- Onboard a Bitbucket App to SSPM
- Onboard a BlueJeans App to SSPM
- Onboard a Box App to SSPM
- Onboard a Bright Security App to SSPM
- Onboard a Celonis App to SSPM
- Onboard a Cisco Meraki App to SSPM
- Onboard a ClickUp App to SSPM
- Onboard a Confluence App to SSPM
- Onboard a Contentful App to SSPM
- Onboard a Convo App to SSPM
- Onboard a Couchbase App to SSPM
- Onboard a Coveo App to SSPM
- Onboard a Crowdin Enterprise App to SSPM
- Onboard a Customer.io App to SSPM
- Onboard a Databricks App to SSPM
- Onboard a Datadog App to SSPM
- Onboard a DocHub App to SSPM
- Onboard a DocuSign App to SSPM
- Onboard an Envoy App to SSPM
- Onboard an Expiration Reminder App to SSPM
- Onboard a Gainsight PX App to SSPM
- Onboard a GitLab App to SSPM
- Onboard a Google Analytics App to SSPM
- Onboard a Google Workspace App to SSPM
- Onboard a GoTo Meeting App to SSPM
- Onboard a Grammarly App to SSPM
- Onboard a Harness App to SSPM
- Onboard a Hellonext App to SSPM
- Onboard an IDrive App to SSPM
- Onboard an Intercom App to SSPM
- Onboard a Jira App to SSPM
- Onboard a Kanbanize App to SSPM
- Onboard a Kanban Tool App to SSPM
- Onboard a Kustomer App to SSPM
- Onboard a Lokalise App to SSPM
- Onboard a Microsoft Azure AD App to SSPM
- Onboard a Microsoft Outlook App to SSPM
- Onboard a Microsoft Power BI App to SSPM
- Onboard a Miro App to SSPM
- Onboard a monday.com App to SSPM
- Onboard a MongoDB Atlas App to SSPM
- Onboard a MuleSoft App to SSPM
- Onboard a Mural App to SSPM
- Onboard an Office 365 App to SSPM
- Onboard an Okta App to SSPM
- Onboard a PagerDuty App to SSPM
- Onboard a RingCentral App to SSPM
- Onboard a Salesforce App to SSPM
- Onboard an SAP Ariba App to SSPM
- Onboard a ServiceNow App to SSPM
- Onboard a Slack Enterprise App to SSPM
- Onboard a Snowflake App to SSPM
- Onboard a SparkPost App to SSPM
- Onboard a Tableau Cloud App to SSPM
- Onboard a Webex App to SSPM
- Onboard a Workday App to SSPM
- Onboard a Wrike App to SSPM
- Onboard a YouTrack App to SSPM
- Onboard a Zendesk App to SSPM
- Onboard a Zoom App to SSPM
- Onboarding an App Using Azure AD Credentials
- Onboarding an App Using Okta Credentials
- Register an Azure AD Client Application
- View the Health Status of Application Scans
- Delete SaaS Apps Managed by SSPM
Onboarding an App Using Azure AD Credentials
To access an administrator account for an app through Azure Active Directory (AD)
single sign-on (SSO), SSPM requires your Azure credentials and an MFA secret key that Azure
generates.
Depending on the app that you are onboarding,
you might have the option to connect SSPM to the app by using administrator
credentials. For some apps, you can access the administrator account through Azure
Active Directory (AD) single sign on (SSO) instead of using direct authentication to
the app.
Connecting to the administrator account through Azure AD provides an extra layer of
security, because this onboarding method uses multi-factor authentication (MFA) to
access the administrator account. To enable MFA, you configure the Azure AD account
to require MFA that uses time-based one-time passcodes (TOTPs). Authenticator apps,
such as Microsoft Authenticator or Google Authenticator, generate the TOTPs by using
an MFA secret key. The MFA secret key is a shared secret between Azure AD and the
authentication app for generating matching passcodes for verification. When you
onboard an app using Azure AD credentials, you must provide SSPM with the MFA secret
key. Like an authenticator app, SSPM will use the MFA secret key for passcode
generation.
In Azure AD, you configure an account to require TOTPs by enabling OATH tokens for
the account.
- Enable MFA using OATH TOTP for the app administrator's Azure AD account.
- Open a web browser and navigate to the Azure portal. Log in using an administrator assigned to the Global Admin role. You can log in as the app administrator whose credentials you will supply to SSPM, or as a different administrator.
- In the Azure portal, navigate to the authentication methods policies page (Authentication methodsPolicies).
- In the Method list, select Third-party software OATH tokens.
- On the settings page for third-party software OATH tokens, make sure the method is enabled. Make sure that the app administrator whose credentials you will supply to SSPM is included in the target group for the method.
Generate and copy an MFA secret key.If the app administrator's account is already configured for MFA, and if you know the MFA secret key value, you don't need to complete the following steps. You need only provide the MFA secret key to SSPM during the onboarding process. If the app administrator's account isn't configured for MFA, complete the following steps. If the app administrator's account is already configured for MFA but you don't know the MFA secret key, reregister the account for MFA and complete the following steps:- Decide which authentication app you will use and download it to your cellphone. You can use the Microsoft Authenticator app or another app that supports TOTP generation, such as Google Authenticator.
- Log in to Microsoft using the app administrator account whose credentials you will supply to SSPM. You can log in from the URL aka.ms/MFASetup. Because MFA using TOTP is now required, the login dialog will notify you that more information is required. Continue to the Next page of the dialog.
- The login dialog prompts you to configure your cellphone with the Microsoft Authenticator app or with a different authenticator app. If you installed Microsoft Authenticator on your cellphone, continue to the Next page of the dialog. If you installed a different authenticator app on your cellphone, click I want to use a different authenticator app.
- Follow the onscreen instructions for setting up the authenticator app,
but, when you are presented with a QR code that contains the MFA secret
key, don't scan it with your authenticator app. Instead, you will first
copy the MFA secret key:
- On the page of the dialog that displays the QR code, click
Can't scan image?.The dialog displays the MFA secret key as a character string in addition to the QR code.
- Copy the MFA secret key into a text file.Do not continue to the next step unless you have copied the MFA secret key. You must provide this key to SSPM during the onboarding process.
- Continue configuring your authenticator app by scanning the QR code or by manually entering the MFA key. Complete the remaining setup steps as prompted by the dialog.
- On the page of the dialog that displays the QR code, click
Can't scan image?.