locked
Azure versus Azure Stack App Service Source Control repository for continuous deployment delivery pipeline RRS feed

  • Question

  • Hi,

    Do you know why we need to configure Source control repository at both the App Service Resource provider level and App Service instance level in Azure Stack?

    If I compare with App Service in (public) Azure, as a user of Azure, I just need to deploy an App Service (for example a Web App Service) and then configure the source control repository at the Deployment option level for the Web App service instance.

    Best regards

    Denis 

    Wednesday, May 10, 2017 12:03 PM

Answers

  • Hi

    Public Azure only exposes the tenant capabilities and in Azure Stack App Service you have Tenant and Admin personas, so in order to expose the feature to your tenants, you need to configure the source control providers as an admin first. 

    In public Azure to expose this tenant capabilities, we (as admins) did something similar to configure the providers.

    Wednesday, May 10, 2017 6:57 PM

All replies

  • Hi

    Public Azure only exposes the tenant capabilities and in Azure Stack App Service you have Tenant and Admin personas, so in order to expose the feature to your tenants, you need to configure the source control providers as an admin first. 

    In public Azure to expose this tenant capabilities, we (as admins) did something similar to configure the providers.

    Wednesday, May 10, 2017 6:57 PM
  • Many thanks for your explanation. It is clear now.

    Best regards

    Denis

    Thursday, May 11, 2017 7:06 AM