Prerequisites: A completed "Add a test app to an existing project" scenario, a Microsoft Entra application registration, and an online sandbox environment called QA with the setup for S2S as specified in task 1 and 2 here completed.
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).
If you are running a free GitHub SKU, you can use the environments setting and a secret with a name of the environment followed by _AuthContext instead of GitHub environments and environment secrets.
-
On github.com, open Settings and Environments in your project. Click New Environment and specify the name of the environment you have created in your tenant and choose Configure environment
-
Under Environment secrets, choose the Add environment secret action. Create a secret called AUTHCONTEXT, and enter a COMPRESSED JSON construct with 3 values: TenantID (where the environment lives), ClientID, and ClientSecret (from the pre-requisites), like:
{"TenantID":"<TenantID>","ClientID":"<theClientID>","ClientSecret":"<theClientSecret>"}.
Note
The secret NEEDS to be compressed JSON and there should NOT be a newline after the secret value.
- Navigate to Actions, select the Publish To Environment workflow and choose Run workflow. Enter latest in the App version field and the name of your environment or keep the * in the environment to receive the new version field. Click Run workflow.
Note
The default app version is current, which refers to the latest release (current version in the market) of your app. Since we haven't released a version yet, you have to specify latest.
-
When the workflow completes, you can inspect the output of the workflow.
-
And/or you can open the QA environment, navigate to Customers and see that your very own Hello World message appears.
