Explanation:

Step 1: Create an agent pool
AzurePipelines provides a pre-defined agent pool named Azure Pipelines with Microsoft-hosted agents.
Step 2: Create a deployment group
Deployment groups make it easy to define logical groups of target machines for deployment, and install the required agent oneach machine.
Step 3: Execute the Azure Pipelines Agent extension to the virtual machines Install the Azure Pipelines Agent Azure VM extension Step 4: Add and configure a deployment group job for the pipeline Tasks that you define in a deployment group job run on some or all of the target servers, depending on the arguments you specify for the tasks and the job itself.
Reference:
https://docs.microsoft.com/en-us/azure/devops/pipelines/release/deployment-groups/howto-provision- deployment-group-agents

Box 1: Create an Azure logic app.
Box 2: Select the HTTP request trigger.
Box 3: Updated the action group in Azure Monitor.
Reference:
https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/action-groups-logic-app

To connect Azure Boards to GitHub.com, connect and configure from Azure Boards. Or, alternatively, install and configure the Azure Boards app from GitHub. Both methods have been streamlined and support authenticating and operating via the app rather than an individual.
Note (see step 4 below):
Add a GitHub connection:
Sign into Azure Boards.
Choose (1) Project Settings, choose (2) GitHub connections and then (3) Connect your GitHub account.
If this is your first time connecting to GitHub from Azure Boards, you will be asked to sign in using your GitHub credentials. Choose an account for which you are an administrator for the repositories you want to connect to.
The Add GitHub Repositories dialog automatically displays and selects all GitHub.com repositories for which you are an administrator. Unselect any repositories that you don't want to participate in the integration.

Reference:
https://docs.microsoft.com/en-us/azure/devops/boards/github/connect-to-github

See the solution below in explanation.
Explanation:
Step 1: Navigate to Personal Access Tokens
* Sign in to Azure DevOps:
* Go to Azure DevOps and sign in with your credentials.
* Access User Settings:
* Click on your profile picture in the top right corner.
* Select User settings.
* Open Personal Access Tokens:
* In the user settings menu, select Personal access tokens.
Step 2: Create a New Personal Access Token
* Create a New Token:
* Click on + New Token.
* Configure the Token:
* Name: Enter Token1.
* Organization: Select the organization where you want to use the token.
* Expiration: Set the expiration to 60 days.
* Set Scopes:
* Code: Select Read, Write, & Manage.
* Build: Select Read & Execute.
* Release: Select Read.
* Create the Token:
* Click on Create.
Step 3: Save the Token
* Copy the Token:
* Once the token is created, copy it immediately as it will not be displayed again.
* Store the token in a secure location.
By following these steps, you will have successfully created a personal access token named Token1 with the specified capabilities and a 60-day expiration