Configure Azure file share prerequisites

Completed by: Azure account holder

Complete Azure account holder setup tasks before the PI Server administrator runs PI bulk import scripts. This setup ensures the target Azure file share is correctly provisioned, accessible, and sized for the expected import volume.

Successful completion of the configuration in this topic provides you with:

• An Azure Storage account resource within your Azure subscription.

• A file share contained within that Storage account to use for the PI bulk import.

• Assignment of the SAS-generation roles to your Microsoft SSO account and file upload access to the PI Server administrator.

  Note: AVEVA is not responsible for any Azure costs incurred during PI bulk import. Users are responsible for their own Azure billing.

To configure Azure file share prerequisites

1. Sign in to your account on the Azure portal.

   Open the Azure portal and sign in with a user account that has admin access to configure storage resources for PI bulk import.

   This access is needed because the Azure admin is responsible for the subscription-level setup, including the storage account, file share, quota, storage tier, import settings, and the role assignments that allow the PI Server administrator (or another designated uploader) to upload the PI Archive files.

2. Switch to the target Azure directory and subscription.

   For directory and subscription switching steps, see Manage Azure portal settings and preferences.

3. Create an Azure Storage account resource for PI bulk imports (or use an existing one) within your Azure subscription.

   A dedicated Storage account resource is required for the PI bulk import workflow. This is an Azure Storage resource within your Azure account or subscription, not a separate Azure sign-in account.

   Before creating or selecting the storage account, ask the CONNECT operator for the target CONNECT site/data store's geography and region. We recommend using an Azure storage account in the same geography as the data store.

   Using an Azure storage account in the same geography as the target CONNECT data store is recommended. Confirm the target data store's geography and region with your CONNECT operator before creating or selecting the storage account.If you need to create a new account, see Create an Azure storage account.

   Account settings:

   Setting	Recommended value	Other supported values	Notes
   Primary service	Azure Files	-	-
   File share billing	Provisioned v2	Pay-as-you-go file shares	-
   Geography	Identical to import target site/data store geography	Any	Co-located file shares and CONNECT data store/sites improve import speeds.

   Tip: Provisioned storage allows you to adjust performance settings, which can speed up the import. These features are not available for Pay-as-you-go file shares.

4. Within your Azure Storage account, select an existing classic file share or create a new classic file share as the storage target for the import.

   Only classic file shares are supported. Blob storage is not supported. If you need to create a file share, see Create an Azure classic file share.

   Before setting the file share capacity, ask the PI Server administrator for the estimated total upload size.

   Configure your classic file share with the following settings:

   Setting	Required value	Notes
   Access tier	Hot or higher	-
   Maximum IO/s	Maximum IO for the duration of the import	Set to maximum during the import, and then restore afterward.
   Maximum capacity	Sized to accommodate the estimated total upload	Use the estimate provided by the PI Server administrator.

5. At the root of the file share, create a directory named CONFIG.

   You will place the four PI Server metadata files in this root-level CONFIG directory later. These files describe the PI Server configuration CONNECT needs to interpret the PI Archive data.

6. Assign the SAS-generation roles to your Microsoft SSO account at the storage account scope.

   On the Azure Storage account that contains the target file share, explicitly assign both Storage File Delegator and Storage File Data Privileged Reader to your own Microsoft SSO account at the storage account scope. These roles are required to generate the SAS URL in the next workflow step. Inherited access does not meet this requirement.

   For portal steps to assign Azure roles, see Assign Azure roles using the Azure portal.

7. Assign Azure access to the PI Server administrator.

   For uploads using Azure CLI with Microsoft Entra authentication, assign Storage File Data Privileged Contributor directly to the PI Server administrator's Microsoft SSO account at the target file share scope. This role allows reading, writing, deleting, and modifying permissions on files, so assigning it at the file share scope limits its reach. Azure CLI uploads using Microsoft Entra authentication also require the --backup-intent option. For details, see Azure Files OAuth over REST and Assign share-level permissions for Azure file shares.Inform the PI Server administrator that Azure prerequisites are complete and they can prepare and stage PI Server migration files for the import.

8. Inform the PI Server administrator that Azure prerequisites are complete and they can prepare and stage PI Archive files for the import.

   Give the PI Server administrator the information listed in Handoff to the PI Server administrator below. They need this information to complete Prepare and stage PI Server migration files.

Handoff to the PI Server administrator

Provide the following information before the PI Server administrator begins file staging:

• The Azure subscription and storage account that contain the target file share.

• The name of the target file share and confirmation that the root-level CONFIG directory exists.

• The file share capacity, tier, and performance settings available for the import.

• Confirmation that the PI Server administrator's Microsoft SSO account has Storage File Data Privileged Contributor assigned directly at the target file share scope for Azure CLI uploads.Any organizational requirements for the historical range, staging method, or import schedule.