Event Collection from Azure Monitor integration failed. Azure Monitor error webhookuriblocked

[Kumar56]

Event collection from Azure Monitor is configured as per doc Event collection from Microsoft Azure Monitor but getting error webhookuriblocked in Azure Monitor when mid server url is attahched. Not sure what is causing the block. Need help

[Abbas_5]

Hello @Kumar56,

The "webhook uri blocked" error in Azure Monitor typically arises when the URL configured in your alert action group isn't accessible or is blocked by Azure's security policies. This often happens when using a Mid Server URL, especially if it's configured with restrictive settings or if Azure Monitor's outbound network rules block access to that specific URL. 

Here's a breakdown of potential causes and troubleshooting steps:

1. Verify Mid Server URL and Network Configuration:

• Check Mid Server Network Rules:

  Ensure your Mid Server's firewall or network security rules allow outbound traffic to Azure Monitor's service endpoint(s). 
• Mid Server URL Correctness:

  Double-check that the Mid Server URL configured in Azure Monitor's action group is accurate and accessible. 
• Authentication:

  If the Mid Server URL requires authentication (e.g., username/password, API keys), make sure those credentials are correctly configured in the Azure Monitor action group. 
• HTTPS:

  Confirm that you're using HTTPS for your Mid Server URL, as Azure Monitor typically requires secure communication for webhooks. 
• Test Independently:

  Use a tool like curl or Postman to send a test request to the Mid Server URL independently to verify that it's accessible and responding as expected. 

2. Azure Monitor Action Group Configuration:

• Secure Webhook:

  Ensure the "Action Type" is set to "Secure Webhook" to utilize Azure Monitor's secure webhook capabilities.
• Authentication in Action Group:

  If your Mid Server URL requires authentication, make sure the appropriate credentials (e.g., API key, token) are added to the action group settings.
• Payload:

  Verify that the JSON payload sent by Azure Monitor to the Mid Server URL is correct and matches the expected format of the Mid Server endpoint. 

3. Network Restrictions and Firewall Issues:

• Azure Firewall or Network Security Groups:

  If your Azure environment has firewalls or Network Security Groups (NSGs), ensure they allow outbound traffic from the Azure Monitor service to the Mid Server's network.
• IP Address Restrictions:

  If your Mid Server URL uses IP address restrictions, make sure Azure Monitor's service IP addresses are allowed. 

4. Troubleshooting Steps:

• Check Azure Monitor Logs:

  Review the Azure Monitor logs for any specific error messages that might provide more clues about the block. 
• Test with a Different URL:

  Temporarily try a public, non-restricted URL to see if the issue is with the Mid Server or Azure Monitor's ability to reach it. 
• Contact Support:

  If you've exhausted the troubleshooting steps and are still facing issues, contact Microsoft Azure Support for assistance. 

  If this is helpful, please hit the thumbs up button and accept the correct solution by referring to this solution in future it will be helpful to them.

  Thanks & Regards,

  Abbas Shaik