-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Meraki Azure Deploy Button Broken #9429
Comments
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal. |
Looks like |
Hi @JustinGrote , Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 24Nov23. Thanks! |
Just manually deploy the connector via this - #8777 (comment) looks like a few things are broken but this is working fine |
@philfy20 I mean, I did that, but probably good to fix the repo so others don't have the same problem, right? |
@philfy20 ,Will check on above issues and get back to you, Thanks. |
Hi @JustinGrote ,Could you please point to exact play book in meraki, Thanks. |
It's literally the deploy button on the README page I linked above. |
@JustinGrote, Noted. Thanks! |
Hi @JustinGrote, we have raised the PR with the corrections. The changes will be reflected once the PR is merged. |
https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/CiscoMeraki
There was an error downloading the template from URI 'https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Playbooks/CiscoMeraki/ConsolidatedTemplate.json'. Ensure that the template is publicly accessible and that the publisher has enabled CORS policy on the endpoint. To deploy this template, download the template manually and paste the contents in the 'Build your own template in the editor' option below.
The text was updated successfully, but these errors were encountered: