With the coming "hardening" of the test environment, it will be more difficult to access the AxDb using Sql. Perhaps with this hardening, Microsoft will also provide an easier way to refresh a development instance, but I think the best solution to this is to allow the Build environment to be a target when making a refresh from production request. This would also make the build environment more useful for smoke testing and troubleshooting.

Ideas Administrator

Thank you for your feedback.

We are not considering the suggestion at this time due to the following reason: The build server by design is only to use EmptyDB or a curated .bak for test automation.  We'll be improving the developer experience to connect to a Azure SQL database so that you don't need to bring large cloud databases in to SQL Server.