问题描述
我是一名顾问，这意味着我可以访问Azure中的几个不同目录（客户端）。另外，我有一个与Visual Studio相关联的MSDN帐户，它可以让我玩一些东西。
I work as a consultant, which means I have access to several different directories(clients) in Azure. Additionally, I have my MSDN account associated with Visual Studio which gives me something to play with.
然而，我经常会来跨场景，我需要一个具有适当组织设置的沙箱环境（例如Azure AD，跨租户的多个订阅，等等）。
I do, however, often come across scenarioes, where I need a sandbox environment with a proper organizational setup(e.g. Azure AD, mulitple subscriptions across one tenant, and so on).
所以当你需要一个配置为企业设置的环境时，我很好奇你在哪里以及如何使用沙箱。
So I was curious where and how you do your sandbox-stuff when you need an environment, which is configured as an enterprise setup.
推荐答案
我们已经组织了我们的QA1，QA2，Prod，DEV1，DEV2，...。使用
We had organized our QA1, QA2, Prod, DEV1, DEV2, ….using
- 使用不同的资源组
- 为您的服务使用不同的前缀命名约定，例如对于azure数据工厂，我们有DEV01_ADF_Sales或DEVIns01_ADF_Sales & NBSP; 
（Ins = Instance）与QA等相同... - 有些情况下你需要更改服务中的内部对象，例如在Azure Logic Apps（ALA）中你可以拥有blob连接，如果你克隆同一个ALA blob连接仍然是相同的，所以在某些情况下你需要将内部
对象名称更改为DEVIns01_Blob_Archive等...
- Use different resource group
- Use a different prefix naming convention for your services, for example for azure data factory we had DEV01_ADF_Sales or DEVIns01_ADF_Sales (Ins = Instance) same thing for QA and etc…
- Some cases you need to change inner objects within your services for example In Azure Logic Apps (ALA) you can have blob connections, if you clone ghe same ALA the blob connection will still be the same, so in some cases you will need to change the inner object name to DEVIns01_Blob_Archive, etc…
关键是......
将您的服务，连接对象和一些内部对象创建到不同的VS项目中，坚持命名约定，您可以简单地替换和翻转部署在同一个租户中从一个名字到另一个名字
Create your services, connection objects and some inner objects into a different VS project, stick to a naming convention and you can simple replace and flip a deployment within the same tenant from one name to another
祝你好运
这篇关于使用Azure开发设置沙箱的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！