Configuring Release Management to work across untrusted domains
Dec 12, 2013Roopesh Nair
Summary
This post details the configuration steps for Release Management (RM) Server and Deployment Agent to work across untrusted domains. It outlines the creation of a local 'Shadow Account' on each machine, its addition to the Administrators group, and its configuration within Release Management with 'Service User' and 'Release Manager' permissions. For the Release Management Client, it describes configuring a Windows Credential in the Credential Manager on the client machine to enable authentication to the RM Server in a different domain.
More from the Azure DevOps Pipelines for Dev-to-Prod Promotion trail
- Azure Developer CLI: From Dev to Prod with Azure DevOps Pipelines
- Azure Developer CLI: From Dev to Prod with One Click
- February Patches for Azure DevOps Server
- Revolutionizing Requirement Gathering: Azure DevOps Meets Azure OpenAI using Semantic kernel
- Deploy a Java application to Azure App Service using GitHub Actions