Things to look at on your storage account
When you use a storage account you already had
When you choose an existing storage account, ShareMaster checks it against how it would have built one and lists the differences. It never changes them for you - the account may be shared with other systems. Each can be changed in the Azure portal: open https://portal.azure.com, then your storage account.
Reads only. Nothing in SharePoint is changed.
What it tells you
- None of these stops archiving. They are what an archive of your documents should be protected against.
- Change only what you are sure nothing else relies on. When unsure, ask whoever owns the account.
Where to change each one
- Anonymous (public) access is allowed. Settings > Configuration > Allow Blob anonymous access: set to Disabled and Save. With it on, a container set to public could be read by anyone with the link.
- Account key (shared key) access is allowed. Settings > Configuration > Allow storage account key access: set to Disabled and Save. ShareMaster never uses the key; anything else that does will stop working, so check first.
- TLS is below 1.2, or HTTPS is not required. Settings > Configuration: set Minimum TLS version to Version 1.2 and Secure transfer required to Enabled, then Save.
- Blob versioning is off. Data management > Data protection: tick Enable versioning for blobs and Save. Without it an overwritten or damaged archived file could not be recovered.
- Then press Read my Azure. Back in Configure tenant, press Read my Azure and choose the account again. The list is read fresh.
What you need
- Contributor (or Storage Account Contributor) on the storage account.
Read next
- Step 2: Configure Blob Storage: How an account ShareMaster creates is locked down.
- Back to contents: The other steps and how they fit together.