---
title: "Microsoft Azure"
canonical: "https://docs.infoblox.com/space/UniversalAssetInsights/1501299419/Microsoft%20Azure"
format: markdown
---
> ⚠️ Discovery data updates for DNS and IPAM are not supported if your account is configured with only the Infoblox Threat Defense license entitlement.

There are multiple pre-requisite configuration steps involved in configuring Azure before configuring Universal Asset Insights in the Infoblox Portal. Failing to follow the pre-requisite configuration stages in Azure will lead to errors. Follow each step shown in the flowchart. You can skip the step that is not applicable to your deployment. For example, if you do not have multi-subscription in Azure, you can skip the step.

The following diagram shows various configuration steps. To access detailed information about a specific step, simply click on the corresponding step:

![Azure_decision_final.drawio-2.png](media://ca657214-a2cb-4513-b375-6dcdbbe76be8)



> Macro (excerpt)
> 
> > Macro (drawio)

The topics related to each step are available as follows. Perform the steps relevant to your configuration:

- [Creating Azure Client ID + Tenant ID](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneDDI/pages/561446922).
- [Azure Configuration for Static Credentials](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneDDI/pages/368574469).


To create a network discovery configuration for Azure, complete the following:

- Go to **Integrations > Discovery > Cloud.**
- Click **Create > Azure**.

> ℹ️ Before configuring discovery for Microsoft Azure, you must create credentials. For more information, see *[Creating Microsoft Azure Credentials](https://infoblox-docs.atlassian.net/wiki/spaces/UniversalAssetInsights/pages/1690567008)*.

> ⚠️ When a provider discovery job is deleted in Universal DDI, the DNS zone that was synchronized through that job remains in its original DNS view (for example, *default*), but it is no longer linked to any cloud provider and it will no longer participate in cloud synchronization. If a new discovery job is later created using the same DNS view name, UDDI automatically generates a new provider-linked DNS view (for example, *default-1*) to preserve the integrity of provider associations. To ensure that DNS record updates continue to synchronize with the cloud provider, administrators must add or modify records within the zone that resides under the active provider-linked view (such as *default-1*), rather than in the old, unsynchronized view (*default*).

Configure the following settings in the wizard:

> Macro (children)