# Global settings[¶](https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/tenant-settings.html#global-settings "Permalink to this headline")

There are only a few global settings in Fleet Manager, accessible from the “Cloud Setup” screen.

## Azure authentication[¶](https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/tenant-settings.html#azure-authentication "Permalink to this headline")

Fleet Manager needs to perform various calls to the Azure API in order to manage resources.

When you deploy Cloud Stacks using the recommended guided setup, the Fleet Manager virtual machine has a User Assigned Managed Identity with Contributor access to the Resource Group, which it uses.

## License[¶](https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/tenant-settings.html#license "Permalink to this headline")

In order to benefit from most capabilities, you’ll need a Dataiku License or Dataiku License Token. You need to enter it here.

## HTTP proxy[¶](https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/tenant-settings.html#http-proxy "Permalink to this headline")

Fleet Manager can run behind a proxy. Once you define at least a proxy host and port, Fleet Manager will use it to access different resources through HTTP:

* to fetch new DSS image lists

* to update or verify licenses

* to log users in with the OpenID Connect protocol

The calls to Azure services won’t be proxied. As such, please make sure the following Azure services you require are reachable from the Fleet Manager virtual machine: Azure Resource Manager, Virtual Network, Storage, Azure Key Vault. You can for example use Service Tags to open access to Azure services in your network security group.
