{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/", "slug": "dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map", "url": "https://update.dsesecurity.com/updates/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/" }, "title": "Normalize country names and codes before aggregating a workbook map", "summary": "Why can one country appear as separate items in an Azure workbook map?", "format": { "slug": "guide", "name": "Guide" }, "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:24:07+00:00", "modified_at": "2026-09-10T02:08:04+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 242, "potentially_affected": "Azure workbook maps combining monitoring rows identified by country or region names and codes.", "dse_recommendation": "Choose one reviewed geographic key representation before grouping the map's monitoring data.", "primary_source": { "name": "Azure Workbooks map visualizations - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-map-visualizations", "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

Azure workbook maps group matching country or region names and matching codes, but a country name and its code are not combined into one map entity. The visualization also has separate aggregation settings for marker size and color. Latitude/longitude mode behaves differently: each row is shown as a distinct item. The selected location mode therefore affects how rows become map items. Microsoft Learn.

\n

Applicability

\n

Use this review when a map combines data from sources with different location representations or when totals appear split across apparently equivalent geography. Establish which field and location mode the map actually uses before interpreting its markers.

\n

DSE recommendation

\n

Choose one reviewed geographic key representation before grouping the map’s monitoring data. Have the data owner document the name-to-code mapping and how unknown or unmapped values are handled. Review size and color aggregation independently so the legend describes each displayed quantity accurately. Do not correct an apparent duplicate by deleting source rows until their identities and intended grouping have been understood.

\n

Verification

\n

Build a small synthetic dataset containing a country name, its corresponding code and an unknown value. Compare the configured map items and displayed metrics with the intended normalized grouping. Confirm that the underlying totals remain accounted for after the transformation. Preserve the field mapping, location mode and aggregation choices with the test result; a visually clean map does not itself prove correct geographic consolidation.

\n

Official references

\n

Microsoft Learn: Workbook map visualization. Source reviewed September 9, 2026.

", "content_text": "Source facts\nAzure workbook maps group matching country or region names and matching codes, but a country name and its code are not combined into one map entity. The visualization also has separate aggregation settings for marker size and color. Latitude/longitude mode behaves differently: each row is shown as a distinct item. The selected location mode therefore affects how rows become map items. Microsoft Learn.\nApplicability\nUse this review when a map combines data from sources with different location representations or when totals appear split across apparently equivalent geography. Establish which field and location mode the map actually uses before interpreting its markers.\nDSE recommendation\nChoose one reviewed geographic key representation before grouping the map’s monitoring data. Have the data owner document the name-to-code mapping and how unknown or unmapped values are handled. Review size and color aggregation independently so the legend describes each displayed quantity accurately. Do not correct an apparent duplicate by deleting source rows until their identities and intended grouping have been understood.\nVerification\nBuild a small synthetic dataset containing a country name, its corresponding code and an unknown value. Compare the configured map items and displayed metrics with the intended normalized grouping. Confirm that the underlying totals remain accounted for after the transformation. Preserve the field mapping, location mode and aggregation choices with the test result; a visually clean map does not itself prove correct geographic consolidation.\nOfficial references\nMicrosoft Learn: Workbook map visualization. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nAzure workbook maps group matching country or region names and matching codes, but a country name and its code are not combined into one map entity. The visualization also has separate aggregation settings for marker size and color. Latitude/longitude mode behaves differently: each row is shown as a distinct item. The selected location mode therefore affects how rows become map items. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-map-visualizations).\n\n## Applicability\n\nUse this review when a map combines data from sources with different location representations or when totals appear split across apparently equivalent geography. Establish which field and location mode the map actually uses before interpreting its markers.\n\n## DSE recommendation\n\nChoose one reviewed geographic key representation before grouping the map’s monitoring data. Have the data owner document the name-to-code mapping and how unknown or unmapped values are handled. Review size and color aggregation independently so the legend describes each displayed quantity accurately. Do not correct an apparent duplicate by deleting source rows until their identities and intended grouping have been understood.\n\n## Verification\n\nBuild a small synthetic dataset containing a country name, its corresponding code and an unknown value. Compare the configured map items and displayed metrics with the intended normalized grouping. Confirm that the underlying totals remain accounted for after the transformation. Preserve the field mapping, location mode and aggregation choices with the test result; a visually clean map does not itself prove correct geographic consolidation.\n\n## Official references\n\n[Microsoft Learn: Workbook map visualization](https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-map-visualizations). 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-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/", "url": "https://update.dsesecurity.com/updates/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Normalize country names and codes before aggregating a workbook map", "item": "https://update.dsesecurity.com/updates/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/", "url": "https://update.dsesecurity.com/updates/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/", "headline": "Normalize country names and codes before aggregating a workbook map", "description": "Why can one country appear as separate items in an Azure workbook map?", "abstract": "Why can one country appear as separate items in an Azure workbook map?", "articleBody": "Source facts\nAzure workbook maps group matching country or region names and matching codes, but a country name and its code are not combined into one map entity. The visualization also has separate aggregation settings for marker size and color. Latitude/longitude mode behaves differently: each row is shown as a distinct item. The selected location mode therefore affects how rows become map items. Microsoft Learn.\nApplicability\nUse this review when a map combines data from sources with different location representations or when totals appear split across apparently equivalent geography. Establish which field and location mode the map actually uses before interpreting its markers.\nDSE recommendation\nChoose one reviewed geographic key representation before grouping the map’s monitoring data. Have the data owner document the name-to-code mapping and how unknown or unmapped values are handled. Review size and color aggregation independently so the legend describes each displayed quantity accurately. Do not correct an apparent duplicate by deleting source rows until their identities and intended grouping have been understood.\nVerification\nBuild a small synthetic dataset containing a country name, its corresponding code and an unknown value. Compare the configured map items and displayed metrics with the intended normalized grouping. Confirm that the underlying totals remain accounted for after the transformation. Preserve the field mapping, location mode and aggregation choices with the test result; a visually clean map does not itself prove correct geographic consolidation.\nOfficial references\nMicrosoft Learn: Workbook map visualization. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:24:07+00:00", "dateModified": "2026-09-10T02:08:04+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/" }, "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-469-normalize-country-names-and-codes-before-aggregating-a-workbook-map/#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": "Normalize country names and codes before aggregating a workbook map" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "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": 242, "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": "Azure Workbooks map visualizations - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-map-visualizations" } } ] } }