Azure / Azure/AzureMonitorStarterPacks

not working using existing storage account or log analytics

Open
#194 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Bicep
Stars
65
Forks
31
Avg merge
3d 11h
Merged PRs (30d)
1

Description

There are several issues when deploying to existing resources.

If we deploy this solution using an existing Log Analytics workspace in another resource group, the deployment will fail because it only checks the resource group you're deploying to. Deploying the solution in the same resource group as the existing Log Analytics workspace avoids errors, but in Azure Workbook, the workspace won't appear in the dropdown menu.

If you manually create the storage account, for example, due to CMK requirements, the deployment fails, stating it has no access. All settings were checked and seemed identical. However, there is a difference in the number of containers created in an existing storage account versus a new one, and adding those containers does not resolve the issue.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.