title: Azure API Management with Multiple Environments
body: <p>My organization runs DEV, QA, UAT and Production environments.  Each one of the environments has a different set of backend endpoints.  The guidance provided by Microsoft is extremely vague on how to handle this situation.  I know that I can utilize properties to store the differences.  I can also get copies of all of the configuration utilizing the git repository.  </p>
  
  <p>My question is: How do I promote changes from DEV to QA and so on?  Each git repository is tied to the specific API Management instance.  I could manage more than one git repository, but I feel like that would be a lot of deleting and copying of files.  How have others solved this problem?  Or am I missing the boat in terms of how I should be managing this?</p>