block Microsoft Store Intuneblock Microsoft Store Intune

The request sounded simple: stop people installing Google Chrome. Plenty of our staff already used it and needed to keep it, but we wanted Edge to be the standard browser from here on, and new Chrome installs had to stop.

We already ran application control on our endpoints, so I assumed the job was mostly done. Then I found Chrome turning up on machines where nobody had approved it. Users were installing it from the Microsoft Store.

Most Intune admins run into this eventually. Blocking the Store in Intune is one setting, and it works. But the Store is only one of several ways a standard user can install software on Windows, and closing one door just sends people to the next. This post covers how to block the Store properly, the gotchas that can break your Intune app deployments, and the other routes you need to close if you actually want to control what gets installed.

Blocking the Microsoft Store in Intune

The setting you want is Turn off the Store application. In Intune, create a Settings catalog profile, search for it under Administrative Templates, Windows Components, Store, and set it to Enabled. There’s a device version and a user version. The device version is the one most people want.

Once it applies, opening the Store shows a message saying it’s been blocked by your organisation. Microsoft’s documentation on configuring Store access notes three things worth knowing:

  • Apps already installed from the Store keep updating automatically.
  • Intune can still deploy Store apps to the device, so your managed deployments keep working.
  • Users may still be able to install software using winget if it doesn’t come from the Store.

That last point comes up again further down.

The Windows edition catch

Microsoft states that the CSP behind this setting only works on Windows Enterprise and Education. On Windows Pro, the profile reports as applied in Intune and does nothing.

If you’re on Microsoft 365 E3 or E5, your devices can step up to Enterprise through Windows subscription activation, so check the edition in Intune’s device list before assuming the policy has failed. If your fleet is on Pro, you’ll need to rely more heavily on the other controls later in this post.

You’ll find blog posts suggesting a registry value called RequirePrivateStoreOnly blocks the Store on Pro. Some admins report it works. It isn’t a documented way to do it on Pro, and Microsoft’s Intune guidance points out that the policy behind it still allows winget command-line access to the Store. Microsoft recommends Turn off the Store application instead, and so would I.

Don’t break your own Intune deployments

It’s tempting to keep going and lock down winget as well. There are policies for it: Enable Windows Package Manager, Enable App Installer Default Source and Enable App Installer Microsoft Store Source, all under Desktop App Installer.

Be careful here. Intune’s “Microsoft Store app (new)” deployments use the same Windows Package Manager plumbing behind the scenes. There’s a reported issue on Microsoft’s winget GitHub where disabling Enable Windows Package Manager stopped Intune-delivered Store apps from installing at all. Admins have reported similar breakage after disabling the Store source, particularly on newly enrolled devices.

If you deploy any Store apps through Intune, and the Company Portal is one, leave those winget policies alone or test them on a pilot group for a few weeks first. According to Microsoft’s Intune documentation, Turn off the Store application on its own already blocks users installing from the Store through either the app or winget.exe, without touching Intune’s ability to deploy.

The doors that are still open

With the Store blocked, a standard user without admin rights can still install software three other ways.

Per-user installers from a browser. This is the most common route. Chrome, Zoom, Spotify, Slack, Webex and plenty of others ship installers that put the application in the user’s own profile, under AppData, when the user doesn’t have admin rights. No elevation prompt, no Store, nothing for a Store policy to catch. The user downloads it, runs it, and it’s installed.

winget’s community source. Even with the Store source blocked, the default winget source can install packages that support a per-user install.

Portable apps. Plenty of tools are just an executable that runs from the Downloads folder. Nothing gets installed, so there’s nothing for an install policy to stop.

That’s why blocking the Store on its own doesn’t stop Chrome. If anything, the Store is the most visible route and therefore the easiest one to notice. The others are quieter.

What actually controls installs: application control

The only thing that reliably closes all of these is controlling what’s allowed to run, not what’s allowed to install. If an executable in a user’s profile isn’t allowed to start, it doesn’t matter how it got there.

You have a few options:

  • App Control for Business (formerly Windows Defender Application Control), built into Windows and configurable from Intune under Endpoint security. Microsoft’s guidance is to let apps deployed by Intune run automatically by trusting the Intune Management Extension as a managed installer. Anything a user drops into their profile is blocked unless you’ve allowed it.
  • AppLocker, older but still common, with rules that deny execution from user-writable paths such as %LOCALAPPDATA% and %USERPROFILE%\Downloads.
  • Third-party application control, such as ThreatLocker or Airlock Digital, which work on a default-deny model with a request and approval workflow.

One lesson from my own Chrome hunt: whichever tool you use, check how it treats Store-delivered apps specifically. Store apps install through a different path from a normal installer, and an allow rule written for one may not behave the way you expect for the other. Test with a real install from the Store on a test machine, not just a policy review.

If you’re in Australia working towards the Essential Eight, this is the Application Control strategy, and blocking execution in user profile and temporary folders is part of the requirement at Maturity Level One. Blocking the Store is a useful extra, but it isn’t the control.

Blocking one app while existing users keep it

Our Chrome situation added a wrinkle: block new installs, but leave the people who already rely on it alone. That’s doable with any application control tool, as long as you know who has it.

  1. Find out who already has it. Intune’s Discovered apps report shows each application and the devices it’s on. Export the Chrome entries and you have your list. Microsoft Defender’s software inventory gives the same information if you use it.
  2. Build a device group from that list. Make it a static group so it doesn’t quietly grow.
  3. Write the block rule for everyone else. Deny the application by publisher or file name for all devices, with an exception scoped to the group. In App Control for Business that means two policies, one for each group. In third-party tools it’s usually a policy scoped to a computer group.
  4. Tell people what to do instead. If someone genuinely needs Chrome later, give them a request path. Deploy it through Intune so it’s a managed, machine-wide install that patches properly.

The exception group will shrink over time as people move to Edge, devices are replaced, and you stop adding to it. Review it every few months and remove machines that no longer have the app.

Leave a Reply

Your email address will not be published. Required fields are marked *