From c9f506925c12b59f2e520daa82d246eca67aed0c Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Sun, 9 Jul 2023 20:56:21 +0200 Subject: [PATCH] azure: Document additional auth options --- doc/030_preparing_a_new_repo.rst | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/doc/030_preparing_a_new_repo.rst b/doc/030_preparing_a_new_repo.rst index c944264c8..04c189d07 100644 --- a/doc/030_preparing_a_new_repo.rst +++ b/doc/030_preparing_a_new_repo.rst @@ -523,20 +523,24 @@ Microsoft Azure Blob Storage **************************** You can also store backups on Microsoft Azure Blob Storage. Export the Azure -Blob Storage account name and key as follows: +Blob Storage account name: .. code-block:: console $ export AZURE_ACCOUNT_NAME= + +For authentication export one of the following variables: + +.. code-block:: console + + # For storage account key $ export AZURE_ACCOUNT_KEY= - -or - -.. code-block:: console - - $ export AZURE_ACCOUNT_NAME= + # For SAS $ export AZURE_ACCOUNT_SAS= +Alternatively, if run on Azure, restic will automatically uses service accounts configured +via the standard environment variables or Workload / Managed Identities. + Restic will by default use Azure's global domain ``core.windows.net`` as endpoint suffix. You can specify other suffixes as follows: