New features and changes to ArcGIS Enterprise on Microsoft Azure at this release are described in the following sections.
New or altered functionality in ArcGIS Enterprise Cloud Builder for Microsoft Azure
The following has changed in ArcGIS Enterprise Cloud Builder for Microsoft Azure at this release:
- A new option is available that allows you to use Azure cloud services for all system directories.
- If you choose this option when creating an ArcGIS Enterprise deployment, the portal content directory and the object store are stored in an Azure Blob Storage container and the ArcGIS Server configuration store and directories are stored in the Azure Blob Storage container, Service Bus namespace, and Microsoft Azure Cosmos DB for NoSQL.
- If you choose this option when creating a stand-alone ArcGIS Server site or a federated ArcGIS Server site, the ArcGIS Server configuration store and directories are stored in the Azure Blob Storage container, service bus namespace, and Azure Cosmos DB for NoSQL.
This option does not apply to federated ArcGIS Notebook Server, ArcGIS GeoEvent Server, or ArcGIS Mission Server sites and is available for new deployments only, not upgraded deployments.
- A new option allows advanced users to provide a Microsoft PowerShell script that will run on every machine in the deployment. You could use this option to install patches, import data or files to the machines, or add components to the deployment that isn't included with Cloud Builder. If you add components to a deployment that Cloud Builder doesn't support, you must provide scripts to upgrade those components every time you upgrade the deployment going forward.
This option is available for the following Cloud Builder workflows:
- Creating a deployment—The script runs on all machines in the deployment after the ArcGIS Enterprise, stand-alone ArcGIS Server site, federated ArcGIS Server site, or ArcGIS Pro virtual machine is created.
- Adding machines to a deployment—The script runs after the machines are added to the deployment.
- Adding ArcGIS Data Store machines to an ArcGIS Enterprise deployment—The script runs after the new ArcGIS Data Store type is added to the deployment or additional machines are added to an existing ArcGIS Data Store type.
- Managing machines in the site—The script runs on the existing machines in the deployment.
- Upgrading a deployment—The script runs after the deployment upgrade completes.
- The tile cache data store is no longer supported. Before you use Cloud Builder to upgrade an ArcGIS Enterprise deployment that includes the tile cache data store, you must acknowledge that you have migrated all hosted scene layer caches to the object store. If you upgrade without migrating these caches, the hosted scene layers will not function after you upgrade to 12.0.
Upgrades
Over the last several releases, support for multiple components and item types has changed. Depending on what version you are upgrading from, you may need to remove components or perform an intermediate upgrade before you upgrade an ArcGIS deployment to 12.0. In other cases, changes to components may require you to perform additional tasks after you upgrade. See Upgrade ArcGIS deployments on Microsoft Azure for specific information and instructions.
General changes
At each release, new versions of ArcGIS Enterprise Cloud Builder for Microsoft Azure and the Esri images on Microsoft Azure Marketplace are available.
For information on bug fixes, see the 12.0 Issues Addressed List.