Skip To Content

Move a geoprocessing service's jobs directory to Microsoft Azure storage

At ArcGIS Server 10.7, administrators can change the jobs directory of a geoprocessing service (or multiple geoprocessing services) from a disk location to a Microsoft Azure cloud storage location, leaving other server directories unchanged. If your geoprocessing services consistently have large outputs, you can use this option to scale your storage resources.


If the View output in map image layer option was turned on when you published the web tool, you cannot use cloud storage as the job directory for the resultant geoprocessing service. The service will be corrupted once you make the change in this workflow.

Prepare the Azure environment

You need a Microsoft Azure account to create a storage account and Blob containers and tables.

Create an Azure storage account

The storage account must meet the following requirements:

  • A standard performance storage account is required.
  • This account can be a General-purpose v2 (recommended) or General-purpose v1 account. Blob storage, Block Blob storage, and Azure Files storage accounts are not supported.
  • The Hot access tier is recommended.
  • Other advanced settings of the storage account can be adjusted based on your organization's needs.

Once the storage account is deployed, copy the key1 of the access keys of your storage account, which is needed when you register the account as a cloud store with ArcGIS Server.

Create a Blob container and a table

Create a Blob container and a table in the same storage account. The geoprocessing service cannot identify them if they're in different storage accounts.

Note the exact name of the table you create; you'll use it in ArcGIS Server.

Move the jobs directory to Azure

Once the Azure Blob container and the table are deployed, register the Blob container in ArcGIS Server and change the service properties accordingly.

  1. Sign in to ArcGIS Server Manager and register the Blob container of your storage account with the server.
  2. When the Blob container has been registered as a cloud store, link it to your Azure table using the REST API. Log in to the ArcGIS Server Administrator Directory at
  3. Go to data > items > /CloudStores, locate your new BLOB container, and click edit to open the Edit Data Item endpoint.
  4. In the JSON representation of the item, add the following keypair with the name of your Azure table:

    "tableStore":"<name of Azure table>"

  5. Click Update to confirm.
  6. Return to the home page of the Administrator Directory, and click Services.
  7. Locate the geoprocessing service (or one of the services) you want to configure to use the Azure Blob container, click the service name, and click edit.
  8. In the JSON representation of the service, locate and edit the following keypair with the name of your cloud store:

    "jobsDirectory":"/cloudStores/<name of your cloud store>"

    The name of the cloud store is at the end of its data item URL endpoint in the Administrator Directory.

  9. Click Save Edits to confirm.
  10. If you're configuring multiple geoprocessing services to use the Azure Blob container as their jobs directory, repeat steps 4–9 for each service.

JSON example

In this example, the Azure account has a storage account named mystorageaccount, and there is a Blob container named myblob and a table named mytable in that storage account. The key1 of mystorageaccount is thisisafakekey12345. You want your geoprocessing service, myGPService1, to use Azure storage for its jobs directory.

During the registration process, the Cloud Store Name is azureblob.

When you edit the cloud store properties, the JSON is changed, with "tableStore": "mytable" added to the end.

Edit data item.

  "path": "/cloudStores/azureblob",
  "type": "cloudStore",
  "id": "31245-abcde...",
  "provider": "azure",
  "info": {
    "isManaged": false,
    "connectionString": "abc/def/ghi/jkl/lmn/opq",
    "objectStore": "myblob",
    "tableStore": "mytable"

Then, change the service properties JSON of your geoprocessing service by adding "jobsDirectory": "/cloudStores/azureblob", following "virtualOutputDir": "/rest/directories/arcgisoutput",.

Edit GPServer.

 "serviceName": "myGPService1",
<... removed to save space ...>
  "resultMapServer": "false",
  "maximumRecords": "1000",
  "virtualOutputDir": "/rest/directories/arcgisoutput",
  "jobsDirectory": "/cloudStores/azureblob",
  "portalURL": "https://domain/webadaptor/",
  "toolbox":  <... removed to save space ...>
 "portalProperties": < ...removed to save space... >,
 "extensions": < ...removed to save space... >,
 "frameworkProperties": {},
 "datasets": []