How Do You Enable Map Visuals in Power BI?

How Do You Enable Map Visuals in Power BI?

You drag a country field onto a map visual and get a grey box with a message instead of a map. Nothing is wrong with your data.

Map visuals in Power BI are gated behind switches that are off until somebody deliberately turns them on. There are two of them, in two different places, and they are controlled by two different people.

That is why the usual advice to "check your settings" rarely fixes it. You can tick every box in Power BI Desktop and still see the same grey box, because the one that matters sits in the admin portal.

This guide covers both switches, what to do when you are not the admin, why the gate exists at all, and the part most articles leave out: Microsoft is in the middle of replacing these visuals, so what you enable today is not what you will be using in two years.

What Is the Short Answer?

Two settings have to be on. In the admin portal, the tenant setting is called Map and filled map visuals, and it lives under Integration settings.

In Power BI Desktop, the local option is under File, then Options and settings, then Options, then Security.

The tenant setting wins. If it is off, nothing you do in Desktop will make a map render, and you will see the message "Map and filled map visuals aren't enabled for your org. Contact your tenant admin to fix this."

Not sure which Power BI settings are quietly costing you traffic and conversions? Get a free SEO and analytics audit and find out what your reporting stack is hiding.

If you are the admin, fixing this takes about a minute. If you are not, your job is to raise the right request with the right justification, which is covered further down.

Why Are Map Visuals Disabled by Default?

This is not an arbitrary default. It exists because map visuals send your data somewhere else.

A map cannot draw a city until it knows where that city is. Turning "Manchester" into a latitude and longitude is called geocoding, and Power BI does not do it locally.

The data that leaves your tenant

The classic Map and Filled map visuals pass location values to Bing Maps services for geocoding. That means the place names in your report leave the Power BI service.

If you plot latitude and longitude only, there is nothing to resolve and no location data needs to be sent. The moment you use city, state, postcode or country fields, those values are shared.

Filled maps are stricter still, because the shape lookup needs the location data regardless of how you supplied it.

Why that matters to a governance team

For most organisations this is unremarkable. For a hospital, a bank or a public body, a report that quietly ships customer postcodes to a third-party geocoder is a conversation nobody wants to have after the fact.

So the switch is off, and somebody has to decide to turn it on. That is the whole design, and it is a reasonable one.

It also explains why the admin may push back. The right answer is usually not "turn it on globally" but "turn it on, and here is which reports use it and what fields they pass".

How Do You Turn Map Visuals On?

Work from the top down. The tenant setting first, then the local one, then the report.

1. Open the admin portal. Sign in at powerbi.com with an account that has Fabric administrator or Power BI administrator rights, then open Settings and choose Admin portal.
2. Find the tenant setting. Go to Tenant settings and search for "map". You are looking for Map and filled map visuals under Integration settings. In newer Fabric tenants the same settings are reachable through the OneLake catalog under Govern, then Configurations, then Tenant settings.
3. Enable it and scope it. Toggle it on. You do not have to open it to the whole organisation — you can apply it to specific security groups, which is usually the better answer when a governance team is nervous.
4. Apply the change and wait. Click Apply. Tenant setting changes take a few minutes to propagate, and users may need to refresh or reopen the report before the visual renders.
5. Check the Desktop option. In Power BI Desktop, go to File, then Options and settings, then Options, then Security, and make sure the map and filled map visuals option is ticked. Click OK and reload the visual.
6. Verify in the service, not just locally. A map that renders in Desktop can still fail for a colleague whose session has not picked up the tenant change. Publish and open the report as an ordinary user before you declare it fixed.

The order matters. If you tick the Desktop box first and nothing happens, it is easy to conclude the setting is broken when the tenant switch was never on.

Getting clean location data into your reports starts with clean tracking. Request a free audit and see whether your analytics is actually capturing what you think it is.

What If You Are Not the Admin?

Most people hitting this message have no admin portal access, and the error text is not much help: "contact your tenant admin" tells you nothing about what to ask for.

Send a request that names the setting. "Please enable the Map and filled map visuals tenant setting under Integration settings" is actionable. "Maps don't work" is not.

Then pre-empt the obvious question. Say which report needs it, which location fields it uses, and whether those fields contain anything sensitive.

If your data is already geocoded to latitude and longitude, say so — that is the version of the request least likely to be refused, because no place names are being sent anywhere.

And offer the scoped option. Asking for the setting to be enabled for one security group rather than the entire tenant is a much easier approval to sign off.

Permission gates are rarely the only thing blocking your reporting. Get a free SEO and analytics audit and see what else is quietly switched off.

Why Is My Map Still Blank After Enabling It?

The toggle fixes the permission problem. It does not fix a data problem, and the two produce different symptoms.

A permissions failure gives you a message where the visual should be. A data failure gives you an empty map, or a map with markers in the wrong hemisphere.

The data category is not set

Power BI has to know that a text column is a place, not a label. Select the column, open Column tools, and set Data category to City, State or Province, Country or Region, Postal code, or Place.

Without that, the geocoder is guessing from the values alone, which works for "France" and fails for "Reading".

The place names are ambiguous

There is a Springfield in dozens of US states. There is a Richmond in several countries. A column of bare city names will scatter.

Add a parent column — country, then state — and include both in the visual's Location bucket so the geocoder has context to disambiguate with.

There are too many data points

Map visuals cap how many points they will plot. A customer-level map with hundreds of thousands of rows will render a subset and quietly mislead you.

Aggregate first. Plot by postcode district or city rather than by individual address, and let the user drill down.

Your region is not supported

Some visuals are not available everywhere. The Azure Maps visual in particular has geographic limits, which the next section covers, and sovereign or government clouds are the usual exception for all of them.

Should You Use Azure Maps Instead?

This is the part that changes the answer to the original question, and it is the reason enabling the old visuals is a short-term fix rather than a decision.

The Azure Maps visual is a separate, generally available visual with its own tenant setting. Microsoft's documentation states that in a future release Power BI plans to deprecate the older map visuals and migrate existing reports to Azure Maps.

No timeline has been published, and existing Bing Maps visuals in reports remain available for now. But the direction of travel is not ambiguous.

How the conversion works

Power BI Desktop has a conversion built in. Open a report containing Map or Filled map visuals and it offers an upgrade; choosing Upgrade maps converts all of them in that report, carrying the existing settings across.

You can also convert a single visual from the visual gallery if you would rather do it piece by piece.

Expect one cosmetic difference: bubbles can look smaller after conversion, because the maximum marker size in Azure Maps is smaller than the maximum bubble size in Bing Maps.

The Azure Maps settings are different

Azure Maps has its own tenant settings, and there are three of them rather than one. The first enables the visual. The second governs whether data sent to Azure Maps can be processed outside your tenant's geographic region, compliance boundary or national cloud instance.

That second setting is not optional everywhere. The Azure Maps visual is currently available only in the US and EU, so for tenants outside those regions the visual will not function at all unless it is enabled.

The third allows Microsoft subprocessors to process data, which some features such as the selection tool depend on, and it requires the second setting to be on first.

When not to upgrade

Microsoft's own guidance is to upgrade unless one of a few specific cases applies. Stay on the older visuals if report users need access from China or Korea, if you are physically located in either regardless of where your tenant lives, or if you are in a government cloud.

In those cases the old visuals are not legacy baggage. They are the only option that works.

Reporting decisions like this one compound over years. Book a free audit and get a clear read on where your measurement setup is heading.

What Are the Limitations Worth Knowing?

Enabling maps does not make them a good choice for every question, and a map is one of the easiest visuals to use badly.

A map answers "where", and almost nothing else. If the insight is "the north is up twelve percent", a map makes the reader do arithmetic by eye that a simple ranked list would have done for them.

Bubble size is hard to compare. Humans read length well and area badly, so a bubble map invites systematic misreading of the differences it is showing.

Filled maps exaggerate large, sparsely populated areas. A country-level choropleth of sales will always make Canada and Russia look important.

And geocoding is a dependency you do not control. When the lookup service is slow or a place name stops resolving, your report breaks for a reason that has nothing to do with your data or your model.

Getting the underlying model right matters more than the visual on top of it. If your geography lives in several tables, read our guide to what a semantic model is in Power BI before you build the relationships that feed the map.

How Does This Compare to the Alternatives?

If the tenant setting is never going to be approved, you still have routes to a map.

Pre-geocode your data upstream. If latitude and longitude arrive in the model already resolved, you avoid sending place names out for geocoding, which removes the objection the setting exists to address.

Use a shape-based visual with your own boundaries. This takes more setup and gives you full control over what leaves the tenant.

Or accept that the question does not need a map. A ranked bar chart by region, sorted descending, communicates "which places are doing well" faster than any map and never needs a geocoder.

The honest comparison is that maps are excellent for genuinely spatial questions — routing, catchment, coverage gaps, store proximity — and mediocre for everything else. Enable them for the first kind of question, not because a dashboard looks richer with one on it.

Final Thoughts

Two switches, in two places, controlled by two people. That is the whole mechanism, and once you know it the grey box stops being mysterious.

The tenant setting called Map and filled map visuals is the one that actually gates you, and the Desktop security option is the one you check second. The error message points at the admin for a reason.

What is worth doing differently is treating the fix as temporary. Microsoft has said the older map visuals are planned for deprecation and that reports will be migrated to Azure Maps, so if you are standing up something new and your users are in a supported region, build it on Azure Maps and skip the migration later.

And before you build any of it, be honest about whether the question is spatial. The best map in your report is the one that answers something a bar chart could not.