Log search alert rules using linked storage will require using a managed identity staring July 2024

As of today, when defining a log search alert rule with linked storage, it is not required to explicitly grant permissions to the storage account itself. **Starting July 2024, alert rules using linked storage will require a managed identity to access the linked storage. This requirement will be enforced on alert rules created with API version 2023-12-01 or newer. Creating or updating linked storage rules using an older API version will be blocked.** This change will be rolled out in two phases: 1. July 2024 –log search alert rules requiring linked storage will be blocked for updates using API versions older than 2023-12-01\. Same applies for creation of new rules requiring linked storage. Use API version 2023-12-01 or newer to update your existing rules or create new rules to use workspace linked storage and define managed identity access. 2. September 2024 - all log search alert rules using linked storage that do not use a managed identity will break and stop evaluating. You can use managed identities in log search alert rules using either of these two options: * System assigned managed identity: Azure creates a new, dedicated identity for this alert rule. Since the identity doesn’t have permission to the linked storage, we won't be able to save the query in the linked storage, therefore System assigned managed identity with Linked storage is not supported. * User assigned managed identity: Before you create the alert rule, you [create an identity](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fmanaged-identities-azure-resources%2Fhow-manage-user-assigned-managed-identities%23create-a-user-assigned-managed-identity&data=05%7C02%7CNoga.Lavi%40microsoft.com%7C525f5400efd14283501a08dc7f253bc8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638525045115333165%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=JVdjYNeC7%2F%2BaFYriLZyhqz4J%2BiXcl7SHAy33uMSGt6c%3D&reserved=0) and assign it read permissions for the linked storage in addition to the rule itself. You can use the same identity in multiple alert rules. **Next steps:** * **[How to define linked storage with CMK](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Flogs%2Fcustomer-managed-keys%3Ftabs%3Drest%23how-customer-managed-key-works-in-azure-monitor&data=05%7C02%7CNoga.Lavi%40microsoft.com%7C525f5400efd14283501a08dc7f253bc8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638525045115346502%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=lf1WsM4uxLJxbjMbnIX2LOh2XLYIm84rQ%2F%2FTWYzfvHg%3D&reserved=0)** **?** * **[Managed identities for Azure resources](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fmanaged-identities-azure-resources%2Foverview&data=05%7C02%7CNoga.Lavi%40microsoft.com%7C525f5400efd14283501a08dc7f253bc8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638525045115351062%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=dQi%2FWYGvvB67Z5ajPtD70lztPsINVYCH2QqfwLbxTUA%3D&reserved=0)** * **[Configure Managed Identity in Log Search Alert Rule](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Falerts%2Falerts-create-log-alert-rule%23managed-id&data=05%7C02%7CNoga.Lavi%40microsoft.com%7C525f5400efd14283501a08dc7f253bc8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638525045115355489%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=TCNeP6t8XLCgDfdApvyPYicEMRfDOBq2kU2A2H6CWY8%3D&reserved=0)** * Alerts * Compliance * Features * Security