Reference:
https://docs.microsoft.com/en-us/azure/azure-monitor/logs/manage-access

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 Git commit, you would need to configure a service hook that listens for commit events in your Git 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 project settings 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 trigger the 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 link https://docs.microsoft.com/en-us/azure/devops/service-hooks/overview?view=azure-devops

1 - Create an app
2 - Create a managed service identify.
3 - Congigure the ID and secret for App1
Reference:
https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal

You can use a system-assigned managed identity for a Windows virtual machine (VM) to access Azure Key Vault.
Sign in to Azure portal
Locate virtual machine VM1.
Select Identity
Enable the system-assigned identity for VM1 by setting the Status to On.

Note: Enabling a system-assigned managed identity is a one-click experience. You can either enable it during the creation of a VM or in the properties of an existing VM.
Reference:
https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-nonaad