Configuring Azure as a Slingshot target requires Slingshot version 1.3, an active Azure subscription, and support for SMB3. This is the current default SMB level on EVO, though some internet service providers may not support it. See this Microsoft article for a list of known ISPs that allow/disallow access using SMB3.
If a Storage account does not already exist, this must first be created at the Microsoft Azure Portal.
Create a new Storage account (and Resource group) if needed, and give the account a name:
Note: In addition to billing considerations, there are many security implications and advanced settings outside the scope of this article. The account used here is for demonstration only, to indicate the fields required for a simple authorization.
Click Review + create to validate the account:
Click Create to deploy the service:
Navigate to the Storage Browser for the Storage account and select Blog containers:
Create a dedicated Blob Container and note the name:
Navigate to Access keys in the Security + networking section of the menu and note the Storage account name and one of the generated keys:
In the EVO web interface, navigate to the Slingshot > Settings page:
Click the plus on the Aliases card to add a new alias;
Choose Azure for the Schema;
Enter the Blob Container's Name in the Container field;
Enter the Storage account name in the User field;
Enter one of the keys (key1) in the Password field:
Click Save and allow a few moments for registration. The page should automatically update once registration is completed:
It's now possible to create a replication job with the Azure target. Click the plus in the corner of the Replication jobs card:
Give the job a name and choose the source and destination for the replication job.
In this example, the sys-management share has been selected , the contents of which will be replicated to Azure.
Microsoft Azure is selected from the drop-down menu, which auto-populates the destination with the Alias information.
The job can then be saved and run. Once finished, clicking Last Job Summary provides a summary of the executed job:
The results are confirmed in the Blob Container, where a copy of the summary report is created as well: