Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

365Defender-VulnerabilityManagement deployment fails #11624

Closed
m455954 opened this issue Jan 3, 2025 · 3 comments
Closed

365Defender-VulnerabilityManagement deployment fails #11624

m455954 opened this issue Jan 3, 2025 · 3 comments
Assignees
Labels
Connector Connector specialty review needed

Comments

@m455954
Copy link

m455954 commented Jan 3, 2025

Describe the bug
Microsoft.Web/sites resource fails to deploy as part of M365Defender-VulnerabilityManagement deployment. it eventually fails with timeout, but spends most of the 3 hours in a 'Service Unavailable' state

To Reproduce
Steps to reproduce the behavior:
Ensure you have correct perms in Azure
Use Deploy to Azure in M365Defender-VulnerabilityManagemnt page
Provide subscription, resource group and Log Analytics details click deploy
Wait
Deployment eventually fails

Expected behavior
Deployment succeeds and I can continue with the configuration steps - I've tried this 3 times now with the same rresult

Screenshots
Image
Image

{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"target": "/subscriptions/baaf55ce-b8ec-453c-b1df-2c33c374452b/resourceGroups/Sentinel_Logic_Apps/providers/Microsoft.Web/sites/fa-mdvm-mb",
"message": "The resource provision operation did not complete within the allowed timeout period."
}
}

Desktop (please complete the following information):

  • OS: Windows
  • Browser : Edge
  • Version : Latest
@v-sudkharat v-sudkharat added the Connector Connector specialty review needed label Jan 6, 2025
@v-sudkharat
Copy link
Contributor

Hi @m455954, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks!

@v-sudkharat
Copy link
Contributor

@m455954, Could you please re-deploy it again? if possible, you can also try it in different region (There could be temporary issue with azure services or specific region.) Please let us know if it still has the same issue.

Thanks!

@m455954
Copy link
Author

m455954 commented Jan 10, 2025

I redeployed using a different subscription, resource group and region - and this time it worked :-)

@m455954 m455954 closed this as completed Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connector Connector specialty review needed
Projects
None yet
Development

No branches or pull requests

3 participants