Azure Cloud Account Onboarding Prerequisites
Focus
Focus
Prisma AIRS

Azure Cloud Account Onboarding Prerequisites

Table of Contents

Azure Cloud Account Onboarding Prerequisites

Prerequisites for onboarding an Azure cloud account in Strata Cloud Manager.
Where Can I Use This?What Do I Need?
  • Prisma AIRS AI Runtime in Azure
This section outlines the prerequisites for onboarding an Azure cloud account in Strata Cloud Manager.
Palo Alto Networks is migrating Discovery services to a new infrastructure from the SCM environment to the Multi-Cloud Security Fabric (MSF) platform. This change affects existing customers who have onboarded cloud accounts and requires action. See the section Migrate from Discovery Services.

Create Azure Storage Account

  1. Sign in to your Azure portal.
  2. In the left panel, click on Create a resource.
  3. Search for the Storage account and select it.
  4. Click Create.
  5. Select your Subscription and Resource Group (or create a new one).
  6. Enter a unique Storage account name.
  7. Choose the Region for your storage account.
  8. Select the Performance (Standard or Premium) and Replication options.
  9. Under Networking tab:
    • Under Network access, select Enable public access from selected virtual networks and IP addresses.
    For perimeter firewall IP addresses in specific regions
    CountryRegionIP AddressTotal IPs
    USus-central134.135.174.8915
    USus-central134.173.206.5215
    USus-central134.172.74.25015
    USus-central134.66.246.16415
    USus-central135.225.238.12415
    USus-central135.223.231.16915
    USus-central134.58.60.13015
    USus-central135.238.28.6215
    USus-central134.67.76.4815
    USus-central1104.154.217.1915
    USus-central135.202.179.25315
    USus-central134.123.101.14215
    USus-central135.223.77.15415
    USus-central134.136.4.14315
    USus-central134.136.232.415
    UKeurope-west235.197.230.503
    UKeurope-west234.142.88.1543
    UKeurope-west234.153.135.443
    INasias-south134.47.134.163
    INasias-south134.47.232.1633
    INasias-south135.200.177.1813
    SGasia-southeast134.142.217.1062
    SGasia-southeast134.124.247.2102
    CAnorthamerica-northeast134.118.182.1333
    CAnorthamerica-northeast134.19.130.1713
    CAnorthamerica-northeast134.19.130.163
    DEeurope-west1034.32.8.223
    DEeurope-west1034.32.127.1613
    DEeurope-west1034.32.63.2523
    AUaustralia-southeast134.87.236.1683
    AUaustralia-southeast135.244.93.2043
    AUaustralia-southeast134.40.145.1313
    Refer to Create an Azure storage account for more configurations.
  10. Click Review + create.
  11. Click Create to deploy a Storage account.

Enable Virtual Network Flow Logs for vNet

  1. Sign in to the Azure portal.
  2. To enable Network Watcher, go to the Azure Portal, search for Network Watcher, select your region, and click Enable.
  3. In the Network Watcher pane, select Flow Logs from the left panel.
  4. Click on + Add flow log.
  5. Select your Subscription from the dropdown menu.
  6. Under Flow log type, choose Virtual network.
  7. Select or create a Storage Account where you want to store the logs.
  8. Enter 30 in the Retention (days) field. (This is the maximum number of days that we display the logs in the Strata Cloud Manager discovery dashboard).
  9. Click Review + Create to review your settings, then click Create to apply the configuration.

Enable Audit Logs for Azure OpenAI Traffic

  1. Go to the Azure portal and open your OpenAI resource.
  2. In the navigation pane, select Diagnostic settings → Add diagnostic setting.
  3. Enter Diagnostic setting name.
  4. In the list of log categories, select Request and Response Logs.
  5. Select to enable Archive to a storage account.
  6. Select the applicable Azure Subscription.
  7. Select the Storage account to store the logs.
  8. Save your settings.
    Flow logs and audit logs must be older than 3 hours to be scanned, as Azure continuously overwrites the log file in the storage account. To prevent loss of logs, we only scan files three hours after their creation time, since discovery won't rescan files that have already been processed.

Grant Access to Storage Account from IP Addresses

  1. Go to Storage Accounts in the Azure portal.
  2. Select your Storage Account.
  3. Under Security + networking, click on Networking in the left panel.
  4. Under Firewalls and virtual networks, select Enabled from selected virtual networks and IP addresses.
  5. Under Firewall, add the following IP addresses in the storage account:
    34.71.64.3 34.28.60.186
  6. Click Save to apply the changes.

Assign Azure Roles

To onboard more than one Azure subscription on the same tenant, assign the following roles on the application that your onboarding Terraform has installed in your Azure tenant.
  1. Go to the Azure Portal and select your subscriptions.
  2. In the left panel, navigate to Access Control (IAM).
  3. Click on the Role assignments tab.
  4. Click + Add -> Add role assignment.
  5. Select the roles for each of the required roles:
    • Azure Kubernetes Service Cluster User Role
    • Storage Blob Data Reader
    • Reader
  6. Click Next.
  7. Click Select members, search for the app using the app object ID or the app name.
    The application name is suffixed by "panw".
  8. Select the application, and then click Select.
  9. Click Next.
  10. Click Review + assign to complete the process.

Migrate from Discovery Services

Palo Alto Networks is migrating Discovery services to a new infrastructure. When migrating consider the following:
  • Add the following new perimeter firewall public IP addresses to your Azure storage account allow list. Failure to update the allow list will result in the cloud account being disabled following migration.
  • After the infrastructure migration, existing Azure accounts will be automatically disabled. To re-enable your account, add the new perimeter firewall public IPs to your allow list, then re-enable the account in the portal. These IP addresses are included below.
  • Consider that the Cloud IP Tag (CIPT) continues to function during and after migration even if the Azure account is temporarily disabled. Once re-enabled after updating the IP allow list, CIPT resumes normal polling.
The CIPT enable-account API call is a no-op if CIPT is already enabled.
Refer to the migration instructions provided on the Migrate from Discovery Services page.