Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Adding a Microsoft Azure repository

Updated on April 5, 2022

Add an Azure repository to provide centralized storage, versioning, and metadata support for file storage and knowledge management, for example, to store and source file attachments in cases.

Pega Cloud Services environments do not support adding local file system repositories. Instead, client applications running in Pega Cloud Services environments use a default S3 repository that is preconfigured and optimized for Pega Cloud environments. This repository appears as pegacloudfilestorage in your list of repositories in RecordsSysAdminRepository in Dev Studio. For details, see Pega Cloud Services File Storage.

Note: To create a repository, your access group must have the PegaRULES:RepositoryAdministrator role. To use a repository, your access group must have the PegaRULES:RepositoryUser role.
  1. In the header of Dev Studio, click CreateSysAdminRepository.

  2. Enter a short description of the repository and the repository name and click Create and open.

  3. In the Definition tab, click Select and select the repository type.

  4. In the Blob container field, enter the name of the container registry.

  5. In the Authentication profile field, enter or select the authentication profile to connect to the Azure repository. To create an authentication profile, click the target icon to the right of the Authentication profile field.

  6. In the Root path field, enter the location of the root folder in Azure.

  7. Click Test connectivity to verify the credentials.

  8. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us