#5 Register a customer production environment for Manual Deployment
| *Prerequisites: A completed scenario 4, an online production environment setup for S2S as specified in task 2 here [Using Service to Service Authentication - Business Central | Microsoft Docs](https://go.microsoft.com/fwlink/?linkid=2217415&clcid=0x409), using the same Microsoft Entra application registration as scenario 3* |
[!NOTE] For access to environments, environment secrets, and deployment branches in private or internal repositories, you must use GitHub Pro, GitHub Team, or GitHub Enterprise. (see this). We are considering adding a secondary option for listing environments.
- Following the process in step 3, you can add an environment to the GitHub repository under settings called MYPROD (Production), which maps to a production environment called MYPROD. Remember the AUTHCONTEXT Secret. Apps will NOT be deployed to production environments from the CI/CD pipeline, by adding the (Production) tag, the environment will be filtered out already during the Analyze phase. You need to run the Publish To Environment workflow to publish the apps. Leave the App version as current, which means that the latest released bits are published to MYPROD.
- After running the Publish to Environment workflow, you should see that the app was deployed to the MYPROD environment only.
[!NOTE] If your Business Central environment name contains spaces or special characters, you might need to map your GitHub environment name to your Business Central environment name using the DeployTo setting with an EnvironmentName setting called DeployTo.
"DeployTo<GitHubEnvironmentName>": {
"EnvironmentName": "<Business Central Environment Name>"
}