Docs » Connect to your cloud service provider » Connect your Azure account to Splunk Observability Cloud » Connect to Azure: Guided setup and other options

Connect to Azure: Guided setup and other options πŸ”—

For a list of supported Azure services, see Available Azure integrations.

Note

Splunk is not responsible for data availability, and it can take up to several minutes (or longer, depending on your configuration) from the time you connect until you start seeing valid data from your account.

Connect to Azure with the guided setup πŸ”—

From Splunk Observability Cloud, connect to Azure using the Microsoft Azure guided setup .

Alternatively, you can navigate to the guided setup on your own:

  1. In the navigation menu, select Data Management.

  2. Go to the Available integrations tab, or select Add Integration in the Deployed integrations tab.

  3. In the integration filter menu, go to By Use Case, and select the Monitor Infrastructure use case.

  4. Select the Microsoft Azure tile to open the Microsoft Azure guided setup.

  5. To start configuring the connection to Azure, select New Integration.

Next, fill in the fields as prompted by the guided setup.

1. Define your Azure connection πŸ”—

Complete the following parameters for your integration:

  • Select your Azure environment:

    • Azure Government for an Azure Government instance.

    • Azure for all other Azure connections.

  • Select the rate, in seconds, at which you want Splunk Observability Cloud to poll Azure for metric data, with 60 seconds (default) as the minimum unit, and 600 seconds (10 minutes) as the maximum unit.

  • Select if you want to import metrics and/or metadata.

  • Prepare your Azure account. See Azure authentication, permissions, and supported regions.

2. Establish your Azure connection πŸ”—

To create the integration, enter the following information:

  • Name: Unique name for this connection to Azure. The name field helps you create multiple connections to Azure, each with its own name.

  • Directory ID: Azure Directory ID you saved in a previous step.

  • App ID: The Azure app (client) ID you saved in a previous step.

  • Client Secret: The client secret (password) you saved in a previous step.

3. Select the data to import πŸ”—

Choose the data you want to send to Splunk Observability Cloud:

  • Select the subscriptions you want to monitor.

  • Optional: Select the services you want to monitor. By default, all services supported by Splunk Observability Cloud are selected. Use the pop-up menu to narrow down to specific services. For a list of supported Azure services, see Available Azure integrations.

  • Optional: Add any additional Azure resources or services you want to monitor that are not fully supported by Splunk Observability Cloud. If you add the same resource type to both services and additional services, Splunk Observability Cloud ignores the duplication.

    • Any resource type you specify as an additional service must meet the following criteria:

      • The resource is an Azure generic resource. For resource types that have hierarchical structure, only the root resource type is a generic resource. For example, a Storage Account type can have a File Service type, and a File Service type can have a File Storage type. In this case, only Storage Account is a generic resource.

      • The resource stores its metrics in Azure Monitor. To learn more about Azure Monitor, refer to the Microsoft Azure documentation.

  • Optional: Use the Add Tag button to create a tag if you want to monitor only tagged data sources, filling out the tag name and tag value fields separately to create a tag pair. Only filters containing Azure tags are allowed. Tag names are internally prefixed with azure_tag, so if you’re using the UI you need to supply only the Azure tag name, for example team instead of azure_tag_team.

    • When tagging, Splunk Observability Cloud only allows alphanumeric characters, and the underscore and minus symbols. Unsupported characters include ., :, /, =, +, @, and spaces, which are replaced by the underscore character. If you want to filter using tags in the UI, remember to create filters with _ if you used any of the unsupported characters.

Alternatives to connect to Azure πŸ”—

Connect to Azure using the Splunk Observability Cloud API πŸ”—

You can use the Splunk API to integrate Azure with Splunk Observability Cloud. For instructions on how to connect to Azure through the API, see Integrate Microsoft Azure monitoring with Splunk Observability Cloud in the Splunk developer documentation.

Azure tag filtering configured through the UI applies an OR operator to the name:value pairs that you specify in separate fields. Values for tag name and tag value are what you anticipate for monitored data sources. To apply more complex rules not governed exclusively by the OR operator, connect to Azure through the Splunk Observability Cloud API and modify the contents of the resourceFilterRules field there.

Connect to Azure using Terraform πŸ”—

To connect using Terraform, see Connect your cloud services using Splunk Terraform.

Next steps πŸ”—

After you connect your Azure account to Splunk Observability Cloud, you can do the following:

This page was last updated on Jul 08, 2024.