Self-service deployment FAQ

This article provides answers to some frequently asked questions about self-service deployment. Refer to the known issues list if your scenario isn't listed here.

Access the Azure SQL database

You can access the Microsoft Azure SQL database by following these steps.

  1. From LCS, add a safe list of the IP address of the machine that you use to connect to the Azure SQL database using SQL Management Studio.
  2. Use LCS to request access to see the database credentials. You must provide a reason for requesting access.

As soon as you submit the request, it's automatically approved. Within a minute or two, you are able to see the database access credentials on the LCS environment details page. You can use the credentials to connect to the SQL database.


The credentials are valid for eight hours, and then they expire. After the credentials expire, you have to request access again.

What are the outbound IP ranges for my finance and operations environment?

For any of your external components that have special handling for the outbound IP addresses of requests originating from the AOS, such as a firewall, you can find the outbound IP addresses by using the Service Tag Discovery API or using the downloadable JSON files. For example, an outbound IP address may be explicitly included in a firewall outside your AOS, or an external service may have an allowed list that contains the outbound IP address for your AOS.

The inbound IP address to the AOS is dynamic. This can, and will, change over time as infrastructure changes occur.


The outbound IP address from the AOS is an IP address from the listed ranges based on the Azure region of your deployment. The specific outbound IP address may vary across outbound requests, even from within the same session.

Infrastructure hosting your Microsoft-managed environments is registered as part of the PowerPlatformPlex Service Tag. For more information, see the Service Tag Documentation, such as how to get the specific IP address ranges for components that don't support Service Tags.


Outbound requests may originate from multiple regions within a geo in disaster recovery scenarios that require regional failover within the geography.