Cloudback Docs
HomePricingBlogContactSign In
  • Getting Started
    • What is Cloudback?
    • Installation Guide
    • First Backup Walkthrough
  • Managing Backups
    • Automated Daily Backups
    • Metadata Backups
    • One-Click Manual Backups
    • Setting Backup Schedules
    • Manage Backup Storage
    • Backup Retention Policy
    • Password-Protected Backups
    • Account Settings
    • Bulk Operations
    • Data Deduplication
    • Email Notifications
    • Instant Notifications
    • Archive Name Pattern
  • Data Restoration
    • Download Backups
    • Restore to GitHub
  • Automation
    • Terraform Provider
    • Operations API
  • Dashboard
    • Dashboard Overview
    • Card view
    • Table view
    • Repository Details
    • Backup Details and Metadata
    • Backup Status Badge
  • Storage Configuration
    • Cloudback Managed Storages
    • Customer Managed Storages
    • Replicating Backups
  • Supported Storages
    • Alibaba Cloud Object Storage Service
    • Amazon S3 Bucket via Access Key
    • Amazon S3 Bucket via Access Point
    • Amazon S3 Glacier
    • Amazon S3 Object Tagging
    • Google Cloud Storage Bucket
    • Microsoft Azure Blob Container
    • Microsoft OneDrive Business
    • Microsoft OneDrive Personal
    • OpenStack Swift
    • Wasabi Customer Managed Storage
  • Account and Billing Management
    • Payment Methods
    • GitHub Organizations
    • Invoiced Customers
  • Troubleshooting and Support
    • Known Issues
    • Contact us
  • Security Features
    • Access Review: Vanta Integration
    • Immutability: Amazon S3 Object Lock
    • Encryption: Password-Protected Archives
    • Traceability: Audit Log
  • Legal
    • Terms of Service
    • Privacy Policy
Powered by GitBook
LogoLogo

Learn more

  • Integrations
  • Blog

Explore

  • Roadmap
  • Changelog

Support

  • Contact Us
  • Status

Legal

  • Terms of Service
  • Privacy Policy

© 2025 Cloudback

On this page
  • About Microsoft Azure Blob Containers
  • Set up Microsoft Azure Blob Container as a customer managed storage
  • Create a new Microsoft Azure Blob Container
  • Set up storage settings
  • Create new Azure Storage Container
  • Create new Shared Access Signature
  • Provide Blob SAS URL
  • Save storage
  • Change the storage for a repository
  • Learn more

Was this helpful?

  1. Supported Storages

Microsoft Azure Blob Container

PreviousGoogle Cloud Storage BucketNextMicrosoft OneDrive Business

Last updated 2 months ago

Was this helpful?

One of the ways to back up a using customer managed storage is to use your own Azure Container. Azure Blob Storage is Microsoft's object storage solution for the cloud. Blob storage is optimized for storing massive amounts of unstructured data, therefore it can be used as a storage for GitHub repository backups created by Cloudback.

This page describes how to set up your own Azure Blob Container as a customer managed storage for Cloudback backups of your GitHub repositories. To be able to use your Azure Blob Container as customer managed storage, you need to have an existing Azure storage or create a new one. Also, you should create a new shared access signature for that storage.

About Microsoft Azure Blob Containers

Azure Blob storage is Microsoft's object storage solution for the cloud that is optimized for storing massive amounts of unstructured data. Unstructured data is data that doesn't adhere to a particular data model or definition, such as text or binary data. Azure Storage is a Microsoft-managed service that provides highly available, secure, durable, and scalable cloud storage.

Set up Microsoft Azure Blob Container as a customer managed storage

To set up Microsoft Azure Blob Container as a storage for your backups, follow the steps below.

Create a new Microsoft Azure Blob Container

  • Type a storage name in the Storage name field. Use a name that will help you identify this storage in the future.

  • Select Microsoft Azure Blob Containers from a Storage Provider dropdown:

Set up storage settings

Choose the settings for the storage:

Create new Azure Storage Container

Create new Shared Access Signature

  • Create and Read

  • Write - this permission is required by Azure for multipart uploads of large archives

  • Delete - this permission is required by Cloudback to delete old backups by retention policy. Grant this permission for the retention policy to work correctly.

Provide Blob SAS URL

In the Step 3 field, provide the Blob SAS URL of the SAS created in the previous step. The SAS URL is required so Cloudback can upload backups to the correct container.

Save storage

Change the storage for a repository

Learn more

Deduplication type - enable or disable data deduplication. For more details, please refer to the documentation

Archive type - enable or disable archive password protection. For more details, please refer to the documentation

Archive name pattern - configure the archive name pattern, which is used to generate the name of the backup archive. For more details, please refer to the documentation

To upload backups to Azure Blob Storage, you need to have a container. You can find more information on how to create a container in the . If you already have a container, you can skip this step.

The Shared Access Signature (SAS) is a URI that grants restricted access rights to Azure Storage resources. You can create a new SAS in the Azure Portal using the instructions provided in the . When creating a new SAS, make sure to grant the following permissions:

Deduplication
Password-Protected Backups
Archive Name Pattern
Azure Blob Storage documentation
Azure documentation
Customer Managed Storages
Dashboard Overview
Repository Details
Bulk Operations
Replicating Backups
GitHub repository
Microsoft Azure Blob Containers storage settings
Microsoft Azure Blob Container SAS
  • Navigate to the Storages page by clicking on the Storages link in the left-side navigation pane

  • Click on the + New storage button:

Open the

Cloudback Dashboard

Click on Save button to save the new storage. You can also use a Test button to check if the storage is configured correctly. After saving the storage, you can use it for storing backups of your repositories.

All storage settings can be changed later in the Storages page. To edit the storage settings, click on the Edit button next to the storage you want to edit.

You can change the storage for a particular repository in the page. Also, you can assign it to multiple repositories through the .

Repository Details
Bulk Operations
Add new storage