Troubleshooting Azure Spring Apps in virtual networks

Note

Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.

This article applies to: ✔️ Basic/Standard tier ✔️ Enterprise tier

This article will help you solve various problems that can arise when using Azure Spring Apps in virtual networks.

I encountered a problem with creating an Azure Spring Apps service instance

To create an instance of Azure Spring Apps, you must have sufficient permission to deploy the instance to the virtual network. The Azure Spring Apps service instance must itself grant Azure Spring Apps service permission to the virtual network. For more information, see the Grant service permission to the virtual network section of Deploy Azure Spring Apps in a virtual network.

If you use the Azure portal to set up the Azure Spring Apps service instance, the Azure portal will validate the permissions.

To set up the Azure Spring Apps service instance by using the Azure CLI, verify that:

  • The subscription is active.
  • The location is supported by Azure Spring Apps.
  • The resource group for the instance is already created.
  • The resource name conforms to the naming rule. It must contain only lowercase letters, numbers, and hyphens. The first character must be a letter. The last character must be a letter or number. The value must contain from 2 to 32 characters.

To set up the Azure Spring Apps service instance by using the Resource Manager template, refer to Understand the structure and syntax of Azure Resource Manager templates.

Common creation issues

Error Message How to fix
Resources created by Azure Spring Apps were disallowed by policy. Network resources will be created when deploy Azure Spring Apps in your own virtual network. Please check whether you have Azure Policy defined to block those creation. Resources failed to be created can be found in error message.
Required traffic is not allowlisted. Please refer to Customer Responsibilities for Running Azure Spring Apps in VNET to ensure required traffic is allowlisted.

My application can't be registered

This problem occurs if your virtual network is configured with custom DNS settings. In this case, the private DNS zone used by Azure Spring Apps is ineffective. Add the Azure DNS IP 168.63.129.16 as the upstream DNS server in the custom DNS server.

Other issues

Troubleshoot common Azure Spring Apps issues