[Git issue 122704 : Token expiry: Discussed with Antony, verified the procedure as per his suggestion, added the note with both the Azure Pipeline and GitHub Actions pivots, and reviewed for the freshness pass. ms.date updated

Author: Akhilesh-microsoft

articles/container-apps/tutorial-ci-cd-runners-jobs.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli
 ms.topic: conceptual
-ms.date: 06/01/2023
+ms.date: 09/19/2024
 ms.author: cshoe
 zone_pivot_groups: container-apps-jobs-self-hosted-ci-cd
 ---
@@ -198,6 +198,9 @@ The workflow runs on the `ubuntu-latest` GitHub-hosted runner and prints a messa
 
 To run a self-hosted runner, you need to create a personal access token (PAT) in GitHub. Each time a runner starts, the PAT is used to generate a token to register the runner with GitHub. The PAT is also used by the GitHub Actions runner scale rule to monitor the repository's workflow queue and start runners as needed.
 
+> [!NOTE]
+> Personal Access Tokens (PATs) have an expiry date. It is mandatory to regularly rotate these tokens and ensure they remain valid (not expired) to maintain uninterrupted service.
+
 1. In GitHub, select your profile picture in the upper-right corner and select **Settings**.
 
 1. Select **Developer settings**.
@@ -504,6 +507,9 @@ Create a new agent pool to run the self-hosted runner.
 
 To run a self-hosted runner, you need to create a personal access token (PAT) in Azure DevOps. The PAT is used to authenticate the runner with Azure DevOps. It's also used by the scale rule to determine the number of pending pipeline runs and trigger new job executions.
 
+[!NOTE]
+> Personal Access Tokens (PATs) have an expiry date. It is mandatory to regularly rotate these tokens and ensure they remain valid (not expired) to maintain uninterrupted service.
+
 1. In Azure DevOps, select *User settings* next to your profile picture in the upper-right corner.
 
 1. Select **Personal access tokens**.