choropleth map with problem

Hi,

"Stopped working two weeks ago, no .pbix changes" almost always means the cause is on the platform side, not your model. Targeted checks - in order of how often each one is the culprit:

1) Tenant setting changed by the admin. The most common cause for sudden map blackouts: Fabric admin portal > Tenant settings > Integration settings > "Use Map and Filled Map visuals" was switched off (or restricted to a security group you're no longer part of). Ask your tenant admin to check that one - if disabled, all Maps and Filled Maps go blank instantly across the org. The visual still loads its frame, just no data.

2) Visual deprecation. The classic Filled Map visual has been on a deprecation path - it stopped geocoding new state names in some regions and gets blank tiles. Quick test: drop an Azure Maps visual onto the page with the same data. If Azure Maps renders correctly, your built-in Filled Map is the issue and you should swap to Azure Maps long-term.

3) Data Category got reset. After certain Power BI Desktop updates, the Data Category on text columns can revert to Uncategorized when the model is re-saved. Modeling pane > select your State column > Properties > Data Category = State or Province. Re-apply explicitly even if it looks already set, then refresh.

4) Geocoding cache poisoning. Sometimes Bing's cache returns a cached failure for ambiguous state names ("Para" can be Brazil-Para or Suriname-Para). Quick test: in Power Query, prepend the country to the column (Brazil-Para etc.) and reload. If the map renders again, the underlying issue is geocoding ambiguity, not your model.

5) Personal/Service settings. In Power BI Desktop, File > Options > Security > "Use ArcGIS / Bing maps" must be enabled. After a re-install or a tenant-level reset, that flag can come back unchecked.

A couple of details that would help narrow it down:
- Is the issue only in Power BI Service (after publish) or also in Power BI Desktop?
- Which build of Power BI Desktop are you on (Help > About)?
- Does it work for some State values and not others?

If you confirm the tenant setting and try Azure Maps as a side-by-side test, the cause should fall out very quickly.

Hi,

Thank you for describing the issue and for confirming that your State column is categorized as State or Province and that your privacy / secure options allow the map to be used. That rules out the most obvious local blockers, but filled map / choropleth visuals still depend on tenant policy, Desktop map permissions, and reliable geocoding of your location text—so the visual can stop showing data even when the report file has not changed.

What is most likely when it “used to work” and then stopped without a model change is a change on the platform side: for example, a Fabric/Power BI admin may have turned off or restricted Map and filled map visuals for some or all users. That setting is documented in Microsoft’s Tenant settings index under Map and filled map visuals and controls whether people in the organization can use those built-in map visualizations. If it is disabled—or limited to a security group you are no longer in—reports can appear to load the visual frame while locations no longer resolve as before. Ask your tenant admin to confirm the current value and whether your account is in the allowed set. Note that tenant changes may take a short time to apply everywhere; see About tenant settings for how settings propagate.

- On the Desktop side, please also check File → Options → Security and ensure options that allow ArcGIS / Bing Maps (wording can vary by build) are still enabled; those can revert after an update or reinstall.

- If policy is fine, treat the next two items as data or geocoding checks: in the Modeling pane, clear and re-apply Data category = State or Province on the column (some updates have been reported to “look” correct until the category is set again). If some regions are ambiguous globally (same state name in more than one country), try a Power Query step that prepends the country to the value and refresh—ambiguous names can yield failed geocoding.

- Quick isolation test: add an Azure Maps visual with the same location field. If Azure Maps shows shapes correctly but the classic filled map does not, focus on classic map / Bing path and long-term migration to Azure Maps, subject to your org’s Azure Maps–related tenant settings.

Hope this answer helps and if you need more references, please visit this links: Map and filled map visuals (tenant settings index) · Filled maps and choropleths (Power BI) · About tenant settings · Azure Maps visual

Best,