{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/", "slug": "dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection", "url": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/" }, "title": "Inventory detector coverage before the Application Insights smart-detection migration preview", "summary": "Does migrating smart detection to alerts preserve every existing detector?", "format": { "slug": "checklist", "name": "Checklist" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:22:55+00:00", "modified_at": "2026-09-10T02:11:19+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 246, "potentially_affected": "Existing Application Insights resources evaluating the documented smart-detection-to-alerts migration preview.", "dse_recommendation": "Map every currently relied-on detector to a retained alert rule or an explicit replacement decision before migration.", "primary_source": { "name": "Upgrade Azure Monitor Application Insights smart detection to alerts (preview) - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-smart-detections-migration", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

The Application Insights migration preview creates alert rules for supported smart detectors, but not every former capability survives. Microsoft’s mapping excludes, among others, slow page-load detection and potential-security-issue detection; excluded capabilities stop being supported for the migrated resource. Failure Anomalies already uses an alert rule and needs no migration. A detector disabled before migration remains disabled in its new rule. After migration, configuration uses smart-detection alert-rule templates rather than the Application Insights resource template. Microsoft Learn.

\n

Applicability

\n

This review concerns resources that still face the documented preview transition. Establish the actual current rule inventory and obtain any required preview approval. Do not assume that a similarly named rule represents the same retained capability.

\n

DSE recommendation

\n

Map every currently relied-on detector to a retained alert rule or an explicit replacement decision before migration. Ask the application owner to identify which removed detections matter to the service. Separate deliberate disabled states from accidental omissions, and have the automation owner update the configuration source used after transition. Avoid treating a successful migration operation as proof of unchanged monitoring coverage.

\n

Verification

\n

Compare the resulting rule inventory, enabled states and configuration authority with the approved mapping on a representative resource. Record unresolved replacement work separately from completed migration steps. Inspect the existing Failure Anomalies rule without counting it as a newly converted detector. Preserve the final mapping so later infrastructure deployments can be checked against the intended post-migration design.

\n

Official references

\n

Microsoft Learn: Smart-detection migration preview. Source reviewed September 9, 2026.

", "content_text": "Source facts\nThe Application Insights migration preview creates alert rules for supported smart detectors, but not every former capability survives. Microsoft’s mapping excludes, among others, slow page-load detection and potential-security-issue detection; excluded capabilities stop being supported for the migrated resource. Failure Anomalies already uses an alert rule and needs no migration. A detector disabled before migration remains disabled in its new rule. After migration, configuration uses smart-detection alert-rule templates rather than the Application Insights resource template. Microsoft Learn.\nApplicability\nThis review concerns resources that still face the documented preview transition. Establish the actual current rule inventory and obtain any required preview approval. Do not assume that a similarly named rule represents the same retained capability.\nDSE recommendation\nMap every currently relied-on detector to a retained alert rule or an explicit replacement decision before migration. Ask the application owner to identify which removed detections matter to the service. Separate deliberate disabled states from accidental omissions, and have the automation owner update the configuration source used after transition. Avoid treating a successful migration operation as proof of unchanged monitoring coverage.\nVerification\nCompare the resulting rule inventory, enabled states and configuration authority with the approved mapping on a representative resource. Record unresolved replacement work separately from completed migration steps. Inspect the existing Failure Anomalies rule without counting it as a newly converted detector. Preserve the final mapping so later infrastructure deployments can be checked against the intended post-migration design.\nOfficial references\nMicrosoft Learn: Smart-detection migration preview. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nThe Application Insights migration preview creates alert rules for supported smart detectors, but not every former capability survives. Microsoft’s mapping excludes, among others, slow page-load detection and potential-security-issue detection; excluded capabilities stop being supported for the migrated resource. Failure Anomalies already uses an alert rule and needs no migration. A detector disabled before migration remains disabled in its new rule. After migration, configuration uses smart-detection alert-rule templates rather than the Application Insights resource template. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-smart-detections-migration).\n\n## Applicability\n\nThis review concerns resources that still face the documented preview transition. Establish the actual current rule inventory and obtain any required preview approval. Do not assume that a similarly named rule represents the same retained capability.\n\n## DSE recommendation\n\nMap every currently relied-on detector to a retained alert rule or an explicit replacement decision before migration. Ask the application owner to identify which removed detections matter to the service. Separate deliberate disabled states from accidental omissions, and have the automation owner update the configuration source used after transition. Avoid treating a successful migration operation as proof of unchanged monitoring coverage.\n\n## Verification\n\nCompare the resulting rule inventory, enabled states and configuration authority with the approved mapping on a representative resource. Record unresolved replacement work separately from completed migration steps. Inspect the existing Failure Anomalies rule without counting it as a newly converted detector. Preserve the final mapping so later infrastructure deployments can be checked against the intended post-migration design.\n\n## Official references\n\n[Microsoft Learn: Smart-detection migration preview](https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-smart-detections-migration). Source reviewed September 9, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/", "url": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Inventory detector coverage before the Application Insights smart-detection migration preview", "item": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/", "url": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/", "headline": "Inventory detector coverage before the Application Insights smart-detection migration preview", "description": "Does migrating smart detection to alerts preserve every existing detector?", "abstract": "Does migrating smart detection to alerts preserve every existing detector?", "articleBody": "Source facts\nThe Application Insights migration preview creates alert rules for supported smart detectors, but not every former capability survives. Microsoft’s mapping excludes, among others, slow page-load detection and potential-security-issue detection; excluded capabilities stop being supported for the migrated resource. Failure Anomalies already uses an alert rule and needs no migration. A detector disabled before migration remains disabled in its new rule. After migration, configuration uses smart-detection alert-rule templates rather than the Application Insights resource template. Microsoft Learn.\nApplicability\nThis review concerns resources that still face the documented preview transition. Establish the actual current rule inventory and obtain any required preview approval. Do not assume that a similarly named rule represents the same retained capability.\nDSE recommendation\nMap every currently relied-on detector to a retained alert rule or an explicit replacement decision before migration. Ask the application owner to identify which removed detections matter to the service. Separate deliberate disabled states from accidental omissions, and have the automation owner update the configuration source used after transition. Avoid treating a successful migration operation as proof of unchanged monitoring coverage.\nVerification\nCompare the resulting rule inventory, enabled states and configuration authority with the approved mapping on a representative resource. Record unresolved replacement work separately from completed migration steps. Inspect the existing Failure Anomalies rule without counting it as a newly converted detector. Preserve the final mapping so later infrastructure deployments can be checked against the intended post-migration design.\nOfficial references\nMicrosoft Learn: Smart-detection migration preview. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:22:55+00:00", "dateModified": "2026-09-10T02:11:19+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-541-inventory-detector-coverage-before-the-application-insights-smart-detection/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Inventory detector coverage before the Application Insights smart-detection migration preview" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Checklist", "Information priority" ], "genre": "Checklist", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 246, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Upgrade Azure Monitor Application Insights smart detection to alerts (preview) - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-smart-detections-migration" } } ] } }