runbook | A framework for gradual system automation | DevOps library

Very specifically, Azure Runbooks, do not support query strings. From the documentation:

To receive data from the client, the runbook supports a single parameter called WebhookData. This parameter defines an object containing data that the client includes in a POST request.

The WebhookData parameter has the following properties:

Azure Runbooks has 2 parts to it, triggers and runbooks:

The Runbook (Right Box) only accepts the single WebhookData object to manage variable and data that Azure Runbooks will operate with.

Webhooks (Left Box), handles the triggering, receiving of data and passing it on to the Runbook. Very specifically, the RequestBody is specified as the:

Body of the incoming POST request. This body keeps any data formatting, such as string, JSON, XML, or form-encoded.This body keeps any data formatting, such as string, JSON, XML, or form-encoded.

With this definition, very specifically, even though WebHooks can support query strings, in this case for triggering Azure Runbooks they are explicitly ignored.

Aside, if the end desire is to subscribe to Microsoft Graph events, the "better" way is to use Event Hubs to handle notifications:

Using Azure Event Hubs to receive change notifications differs from webhooks in a few ways, including:

• You don't rely on publicly exposed notification URLs. The Event Hubs SDK will relay the notifications to your application.
• You don't need to reply to the notification URL validation. You can ignore the validation message that you receive.
• You'll need to provision an Azure Event Hub.
• You'll need to provision an Azure Key Vault.

As requested, here my comment as answer

The date format in $DateInName shows it is formatted as 'dd-MM-yyyy'
(2-digit Day, 2-digit Month, 4digit Year).

Either do

This error occurs when the user account that is being used to run the Azure PowerShell cmdlets does not have the correct administrator role .

Get-AzureADUser command uses Azure AD graph in the backend. You may need to add the Application permissions ,Directory.Read.All of AAD graph (Azure Active Directory Graph) and make sure to grant admin consent for the same.

Check support-for-azure-ad-graph-permission

(or)

Go to Azure portal > Azure AD > Roles and Administrators > Select Directory Readers role and assign this role to the runbook required.

Reference: Authorization_RequestDenied error

edit:

You need to add the azure_storage_blob python package in your automation account

Then, you can use the python code below to upload file to azure blob storage from a URL:

Most likely you haven't created an Azure Run As Account. Follow the steps here to do so.

We have tested this in our local environment it is working fine, Below statements are based on the analysis.

In our local environment, We have created a Powershell runbook running with different PowerShell Versions 7.1 & Version 5.1.

• Using the above share Script & webhook URI, when we are trying to invoke the runbook (PowerShell version 7.1) using the `Invoke-webRequest method it is continuously failing.

Alternatively, We have tried to invoke the runbook (PowerShell version 5.1) using the Invoke-webRequest method it is working fine.

We would suggest you to use Powershell Version 5.1 instead of 7.1 in your Runbook.

Here is the sample Output for reference:

I have tested in my environment

I get the same error as yours if I use subprocess in my python script to run PowerShell command

This is because the subprocess module is not able to find the powershell.exe path

For the workaround, you can use either of the options:

1. You can use PowerShell script instead of python script
2. You can use MS Graph API in your python code instead of PowerShell commands

I have tested in my environment

You can use MS Graph API query in your python script to get the Azure AD sign in logs of the users

You can use below python code:

You can use the Start-AzAutomationRunbook cmdlet to trigger a child runbook from the another run book inside the automation account.