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.