Selected AZ-400 Microsoft Azure Questions Answers

Service hooks in Azure DevOps allow you to trigger actions in other tools based on events that occur in your Azure DevOps project. To automatically add release information to work items associated with a Get commit, you would need to configure a service hook that listens for commit events in your Get repository, and then sends the release information to the appropriate work items.

Here's the steps you can follow to set up a service hook for this purpose:

In your Azure DevOps project, navigate to the projectsettings by clicking on the gear icon in the top right corner of the page.

Select "Service Hooks" from the left-hand menu.

Click on the "New Subscription" button to create a new service hook.

In the "Event" drop-down menu, select "Code pushed" to triggerthe service hook when a new code revision is committed to the repository.

In the "Actions" section, select the action that you want to take place when the service hook is triggered. For example, you might use the "Link work items to commits" action to automatically associate work items with the relevant commits.

Configure the remaining settings as needed, and then click on the "Create" button to create the service hook.

You can find more information on Service hooks in Azure DevOps by following this

For containerized applications that serve traffic, you might want to verify that your container is ready to handle incoming requests. Azure Container Instances supports readiness probes to include configurations so that your container can't be accessed under certain conditions.

Personal access tokens (PATs) give you access to Azure DevOps and Team Foundation Server (TFS), without using your username and password directly. These tokens have an expiration date from when they're created. You can restrict the scope of the data they can access. Use PATs to authenticate if you don't already have SSH keys set up on your system or if you need to restrict the permissions that are granted by the credential.