AZ-400 Exam Dumps : Microsoft Azure DevOps Solutions

You can add the text " AB# < WORKITEMNUMBER > " to the title or description of the pull request in GitHub, which will automatically link the request to an existing Azure Boards work item with that number.

Task 8: Create a Service Hook to Integrate with Azure Storage (queue1)

Step 1: Verify the Storage Account and Queue

In the Azure portal ( ):

Go to Storage accounts .

Find the storage48901628 storage account.

In the left menu, click on Queues .

Ensure that a queue named queue1 exists. If not, create it by:

Clicking + Queue .

Enter Name: queue1.

Click OK .

Step 2: Prepare the Storage Account’s Shared Access Signature (SAS)

Azure DevOps uses SAS tokens to send messages to a storage queue.

In the Azure portal , go to the storage48901628 storage account.

In the left menu, click Shared access signature .

Set the following:

Allowed services: Queue.

Allowed resource types: Object.

Allowed permissions: Add, Write.

Start and expiry date/time: Adjust as needed (e.g., 1 year).

Click Generate SAS and connection string .

Copy the Queue SAS URL (e.g.,

Step 3: Create the Service Hook in Azure DevOps

In your Azure DevOps Project (Project1):

In the bottom-left, click Project settings .

In the left menu, click Service hooks .

Click + Create subscription .

Step 4: Configure the Azure Storage Service Hook

In the Create a subscription wizard, choose Azure Storage Queues and click Next .

Choose the Trigger :

For example: Code pushed (or other events you want to send to the queue).

Click Next .

Configure the Action :

Queue endpoint URL: The Queue SAS URL you copied in Step 2 (including the queue1 endpoint and SAS token).

Example:

bash

Copy

Step 5: Finalize and Test the Integration

Click Test to ensure Azure DevOps can send a message to the queue.

If the test succeeds, click Finish to create the service hook.

Step 6: Validate in the Azure Portal

In the Azure portal, go to storage48901628 > Queues > queue1 .

You should see new messages appear in the queue whenever the configured Azure DevOps event (like push or PR) occurs.

C:\Users\wk\Desktop\mudassar\Untitled.jpg