Azure Blob
The AzureBlob Execution Method lets a JAMS Job delete, download, or upload a single Azure Blob. No scripting required. Use it to share, update, and maintain files in your Azure environment on a schedule.
What it can and cannot do
- Operations: Delete, download, or upload.
- Scope: One operation on one path, file, or Blob per Job.
- Not supported: Container-level operations, such as creating a container, deleting a container, or modifying container rules.
Before you begin
Collect the following from Azure:
| Value | Notes |
|---|---|
| Tenant ID | |
| Client ID | The Client application must have the Storage Blob Data Contributor permission on the storage account. |
| Client Secret | Stored in a JAMS Credential (see below). |
| Storage Account Name | |
| Remote Container Name | |
| Blob Name |
Set up JAMS
You only need to do this once per Azure storage account.
1. Create two Credentials
| Credential | Purpose |
|---|---|
| Azure secret | Stores the Azure Client Secret in the Password field. Leave Logon As empty. |
| Job execution | Runs the Job in JAMS. |
See Working with User Credential Definitions for how to create a Credential.
2. Create a Connection Store item
Connecting to an Azure Blob requires a Connection Store item in JAMS. See Connections for Integrations for the configuration steps.
Create the Job
The procedure is the same for all three operations. Only the fields in step 6 differ. Select your operation below.
- Click Definitions from the JAMS Shortcuts menu.
- In the Folder Navigator, click the Folder where the Job will be saved. Create one first if it does not exist. See Working with Folders.
- Click +, enter a Name for the Job, select AzureBlob in the Execution Method field, then click Ok.
- On the Source tab, select your operation in the Blob Operation field.
- Click Continue. The operation you selected is displayed in the Blob Operation field.
- In the Azure Blob Connection field, select the Connection Store item you created, then complete the remaining fields for your operation:
- Delete
- Download
- Upload
| Field | Value |
|---|---|
| Remote Container Name | The name of the container. |
| Blob Name | The name of the Azure Blob to delete. |
Deleting a Blob also deletes any snapshots of it. Snapshots cannot be recovered.
| Field | Value |
|---|---|
| Remote Container Name | The name of the container. |
| Blob Name | The name of the Blob. |
| Local Path | The path, including the parent folder, where the Blob will be downloaded on your local machine. |
| Local File Name (optional) | The name to give the downloaded file. |
If the file already exists on your local machine, it is overwritten.
| Field | Value |
|---|---|
| Remote Container Name | The name of the container. |
| Blob Name | The name of the Blob in Azure. |
| Local Path | The path, including the parent folder, to the file you are uploading. |
| Local File Name | The name of the file, including the file extension. |
If a Blob with the same name already exists in Azure, it is overwritten.
- Click the Schedule tab and add schedule items to set when the Job runs.
- Click the Properties tab, then:
- In Execute As, select the JAMS Credential that runs the Job.
- In Agent, select the Agent, but only if the Job will not run on the Scheduler.
- Click Save and Close.
Cancel a running Job
- Click Monitor from the JAMS Shortcuts menu.
- Right-click the running Job and select Cancel.
- Click Yes.
What happens next depends on the operation:
| Operation | Result of cancelling |
|---|---|
| Delete | Nothing is left behind. |
| Download | A partial file may be saved. |
| Upload | No file is uploaded. |