>
    Strata Copilot
    Begin Scanning a Microsoft Azure Storage App
    Focus
    Download PDF
    Focus
    1. Home
    2. SaaS Security
    3. Data Security Administration
    4. Onboard Sanctioned SaaS Apps to Data Security
    5. Begin Scanning a Microsoft Azure Storage App
    Download PDF
    SaaS Security

    Begin Scanning a Microsoft Azure Storage App

    Table of Contents

    Begin Scanning a Microsoft Azure Storage App

    Authorize Data Security to connect to Microsoft Azure Storage to scan all content shared within the app.
    Where Can I Use This?What Do I Need?
    • Strata Cloud Manager
    • Data Security license
    Or any of the following licenses that include the Data Security license:
    • CASB-X
    • CASB-PA
    In addition to the Data Security license, you must have an Evident Storage license for Data Security to scan for Microsoft Azure Storage assets.
    To connect a Microsoft Azure Storage app to Data Security and begin scanning assets, you need to:
    Support for automated remediation capabilities varies by SaaS application.

    Supported Content

    The following table lists the supported content for the Microsoft Azure Storage app.
    Support For
    Details
    Scan Content
    		Storage Accounts, Containers, Files
    Backward Scan
    Yes
    Forward Scan
    Yes
    Rescan
    No
    Selective Scan
    Yes
    Exposure
    Internal, External, Public
    Remediation Actions
    • User Quarantine—No
    • Admin Quarantine—Yes, only files
    • Change Sharing—Yes, only folders
    Post-Remediation Actions (Actions after Admin Quarantine):
    You can delete, restore, or download a quarantined file after performing a remediation action (for example quarantine or incident generation).
    • Delete—Yes
    • Restore—Yes
    • Download—Yes
    Notifications
    • Notify File Owner—No
    • Notify Via Slack—Yes (applicable only if you have onboarded Slack Enterprise or Slack Pro and Business)
    User Activities
    • Activity Monitoring—Yes
    • Activity Alerting—Yes
    • Folder Monitoring—N/A
    Snippet Support
    Yes
    Known License/Version restrictions
    Supported Versions
    • Business
    • Enterprise
    Caveats/Notes
    None

    Create Your AAD Application

    To discover containers, Data Security requires specific permissions. Permissions are tied to roles, and these roles are bound to the Azure Storage app subscription and an AAD application that you create in advance of adding the Microsoft Azure Storage app on Data Security.
    Item
    Description
    Ensure that you have the required permissions to create an application in Azure Active Directory (AAD).
    Check Azure Active Directory Permissions in the Microsoft documentation.
    Create an AAD Application.
    In a text editor (such as Notepad), copy the App-ID and name of the application to use later in this procedure.
    Create an Azure Active Directory Application in the Microsoft documentation.
    Get the Tenant ID, which is the ID of the AAD directory in which you created the application.
    In a text editor (such as Notepad), copy the Directory (tenant) ID to use later in this procedure.
    The Directory ID value is the tenant ID required to install Azure to Data Security.
    Get Tenant ID in the Microsoft documentation.
    Assign Reader Role to the AAD Application on the subscriptions to scan.
    Assign Storage Account Key Operator Service Role to the AAD Application on the subscriptions or storage accounts to scan.
    Assign Application to Role in the Microsoft documentation.
    Enable roles required by the AAD Application.
    From your subscription select Access control (IAM)AddRole. Enable the following roles:
    • Reader Role (Subscription scans) — The reader role can view existing Azure resources and is required for monitoring subscriptions.
    • Storage Account Key Operator Service Role (Storage Account scans) — The storage account key operator role enables application identity and permissions. This role is required to list and regenerate storage account keys in the Azure key value application.

    Register Your AAD Application

    Before you can add the Microsoft Azure Storage app, you must register the application to provide secure sign-in and authorization for Data Security.
    1. Register your application with an Azure Active Directory tenant.
      1. Log in to Microsoft Azure.
      2. Select Azure Active DirectoryApp registrations.
      3. Do one of the following:
        • Add a New application registration: Enter the application Name and Supported account type and, optionally, URI to Register a new application.
        • Select an application that has already been registered by clicking on the app from the list.
    2. Enable API permissions for Microsoft Graph.
      1. Click on the Display name for the registered app.
      2. Select View API permissionsAdd a permissionMicrosoft Graph.
      3. Add Read all users’ full profiles in Application Permissions and Delegated Permissions.
    3. Enable API permissions for Azure Active Directory Graph.
      Microsoft Azure Active Directory Graph API has been retired. To enable the Directory.Read.All and User.Read.All permissions for Azure Active Directory Graph, see https://learn.microsoft.com/en-gb/graph/migrate-azure-ad-graph-configure-permissions.
    4. Grant application and delegated permissions.
      1. Click on the Display name for the registered app.
      2. Select Grant admin consent for Default Directory.
        A confirmation window displays to grand permissions for all accounts in the current directory. Select Yes to grant the permissions for the accounts.

    Retrieve Required Information from AAD Application

    Now that you’ve registered your AAD application, you must retrieve the following information to complete the setup of the Microsoft Azure Storage app on Data Security. Additionally, to generate the Application Key, you need to create the key as outlined in the final step below.
    • Application (client) ID
    • Directory (tenant) ID
    • Application Key
    1. Log in to Microsoft Azure.
    2. (App-ID) Select the registered app to view and copy the Application ID to enter during app installation.
    3. (Directory ID) Select Azure Active DirectoryProperties. Copy the Directory ID to enter during app installation.
    4. (Application Key) Add and copy the key:
      1. From the registered application, select Certificates & secretsNew client secret, provide a description and set duration to Never, then Add the key.
        The key value is the Application Key to enter during app installation. After saving the key, the value of the key is displayed.
      2. Copy this value because you're not able to retrieve the key later.

    Enable Iterative Scanning Service

    Data Security continuously scans for Azure Storage subscriptions and accounts to identify and report any new accounts, activities, and events with the iterative scanning service. The service also scans and identifies users assigned to subscriptions, resources, groups, containers, and storage accounts.
    To enable iterative scan on Data Security, you need to configure the diagnostic service settings in Azure for each storage account.
    1. Select the storage account to configure the diagnostic service settings.
    2. Select Monitor Diagnostic settings. If not already, enable the settings by turning the status On.
    3. Select the type of Metrics and Logging data for each service you wish to monitor, and the retention policy for the data by moving the retention in days slider from 1 to 365.
    4. Save your monitoring configuration.

    Add the Microsoft Azure Storage App

    To begin scanning a Microsoft Azure Storage app:
    1. (Recommended) Add your Microsoft Azure Storage domain as an internal domain.
      For more information, see Define Your Internal Domains section.
    2. Log in to Strata Cloud Manager.
    3. Select ConfigurationSaaS SecurityData SecurityApplicationsAdd ApplicationMicrosoft Azure Storage.
    4. Configure your Microsoft Azure Storage settings.
      1. Click Connect to Account.
      2. Enter the Directory ID, Application ID, and Application Key you recorded in the previous steps.
      3. Click Next.
    5. Select the Azure subscriptions to monitor.
      1. Enable a Subscription to scan from the discovered list, or you can select Automatically scan all new subscriptions.
      2. Click Next.
    6. Review initial scan discoveries and complete the Azure Storage app installation. View Details on the discovered containers to review the discoveries and determine if you want to proceed with scanning:
      • To proceed scanning all discovered containers, enable Scan all current and any new containers and then Save your scan setting.
      • To proceed scanning individual containers and subscriptions, select the items to scan and then Save your scan setting.
      • If you do not want to proceed with scanning the discovered containers, select Cancel to abort the installation.
      • Save the Azure Cloud Storage app to the list of Cloud Apps.
    7. (Optional) Give a descriptive name to this app instance.
      1. Select the Azure Cloud Storage link on the Cloud Apps list.
      2. Enter a descriptive Name to differentiate this instance of the Azure Cloud Storage app from other instances you are managing.
    8. To start scanning the new Azure Cloud Storage app for risks, select ConfigurationSaaS SecurityData SecurityApplicationsAzure Cloud StorageView Settings...Start Scanning.
      The status changes to Scanning. Data Security starts scanning all assets in the associated Azure Cloud Storage app and begins identifying incidents. Depending on the number of Azure assets, it may take some time for the service to complete the process of discovering all assets and users. However, as soon as you begin to see this information populating on the Dashboard, you can begin to Assess Incidents.
    9. Monitor the scan results.
      During the discovery phase, as Data Security scans files and matches them against enabled default policy rules.
      Verify that your default policy rules are effective. If the results don’t capture all the risks or you see false positives, improve the results.
      (Optional) To view the status of Subscriptions and Containers being scanned, select SettingsCloud App and Scan Settings. Select an Azure Storage app from the list of Cloud Apps and expand the Subscriptions and Containers to view the scan details.

    Identify Risks

    When you add a new cloud app, Data Security automatically scans the cloud app against the default data patterns and displays the match occurrences. You can take action now to improve your scan results and identify risks.
    1. (Optional) Modify match criteria for existing policy rules.
    2. (Optional) Add new policy rules.
      Consider the business use of your app, then identify risks unique to your enterprise. As necessary, add new:
    3. (Optional) Configure or edit a data pattern.
      You can configure data patterns to identify specific strings of text, characters, words, or patterns to make it possible to find all instances of text that match a data pattern you specify.

    Fix Microsoft Azure Storage App Onboarding Issues

    The most common issues related to onboarding a Microsoft Azure Storage app are as follows:
    Symptom
    Explanation
    Solution
    Scan results for subscriptions and containers don't display in SaaS Security web interface.
    Data Security can't discover containers without the correct permissions.
    Create the AAD application and associate your AAD application with the roles under each subscription as outlined in Create Your AAD Application.
    Data Security is not showing assets after onboarding successfully.
    Data Security can't scan storage accounts without the correct permissions.
    Enable Iterative Scanning Service

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