Anavem
Languagefr
How to Block Microsoft Store Web Installer Using Entra Internet Access

How to Block Microsoft Store Web Installer Using Entra Internet Access

Learn to prevent users from bypassing Microsoft Store restrictions by blocking web installer downloads through Entra Internet Access web content filtering policies and complementary Intune configurations.

April 8, 2026 15 min
mediumentra 7 steps 15 min

Why Block Microsoft Store Web Installer Downloads?

Organizations often implement Microsoft Store app restrictions through Group Policy or Intune to maintain security and compliance standards. However, users can easily bypass these restrictions by downloading apps directly from apps.microsoft.com or get.microsoft.com using the Microsoft Store web installer. This creates a significant security gap that traditional Store blocking methods cannot address.

The Microsoft Store web installer allows users to download and install Store apps without using the traditional Microsoft Store application. This bypass method has become increasingly popular among users who want to install restricted applications, potentially introducing unvetted software into corporate environments.

How Does Entra Internet Access Solve This Problem?

Microsoft Entra Internet Access provides web content filtering capabilities that can block specific URLs and domains at the network level, before users can even access the Store web installer pages. Unlike traditional firewall rules or DNS blocking, Entra Internet Access integrates directly with your identity and device management infrastructure, providing granular control based on user identity, device compliance, and conditional access policies.

This tutorial demonstrates how to implement a comprehensive blocking strategy using Entra Internet Access as the primary mechanism, supplemented by Intune device configuration policies and AppLocker rules. This multi-layered approach ensures that users cannot bypass Store restrictions through web browsers while maintaining the functionality of legitimate Store operations like app updates for already-installed applications.

By the end of this guide, you'll have deployed a robust solution that blocks Store web installer downloads across your organization while preserving essential Microsoft Store functionality for system updates and approved applications.

Implementation Guide

Full Procedure

01

Enable Entra Internet Access and Access the Web Content Filtering Console

First, you need to access the Microsoft Entra admin center and navigate to the Internet Access web content filtering section. This is where you'll create the primary blocking policy.

Open your browser and navigate to the Entra admin center:

https://entra.microsoft.com

Sign in with your Global Admin or Security Admin credentials. Once logged in, navigate to the Internet Access section:

  1. Click Protection in the left navigation pane
  2. Select Internet Access
  3. Click Policies
  4. Select Web content filtering

If this is your first time using Internet Access, you may need to enable the service. Click Enable Internet Access if prompted and wait for the service to initialize (typically 2-3 minutes).

Pro tip: Bookmark the direct URL https://entra.microsoft.com/protection/internetaccess for quick access to Internet Access policies.

Verification: You should see the Web content filtering dashboard with options to create new policies. If you see a "Service not available" message, ensure your tenant has the required licensing.

02

Create a New Web Content Filtering Policy for Store Blocking

Now you'll create a specific policy to block Microsoft Store web installer downloads. This policy will target the primary domains used by the Store web installer.

In the Web content filtering dashboard, create a new policy:

  1. Click + New policy
  2. Enter the policy name: Block Microsoft Store Web Installer
  3. Add a description: Prevents users from downloading apps via apps.microsoft.com and get.microsoft.com
  4. Set the policy state to Enabled

Configure the URL blocking rules by adding these specific domains:

*.apps.microsoft.com
*.get.microsoft.com
store.rg-adguard.net
*.microsoft.com/store/apps

For each URL pattern:

  1. Click Add URL category
  2. Select Custom category
  3. Enter the URL pattern
  4. Set the action to Block
  5. Add a block message: Access to Microsoft Store web installer is blocked by your organization's security policy.
Warning: Do not use broad patterns like *.microsoft.com as this will break essential Microsoft services including Windows Update and Office 365.

Verification: Your policy should show 4 custom URL categories, each set to "Block" action. The policy status should display as "Enabled".

03

Configure Policy Assignment and Targeting

Next, you need to assign the policy to the appropriate users and devices. This step determines which users will have the Store web installer blocked.

In your newly created policy, configure the assignments:

  1. Click the Assignments tab
  2. Under Include, select one of these options:

For organization-wide blocking:

Include: All users
Exclude: IT Admin group (recommended)

For targeted deployment:

Include: Specific security groups
- Standard Users
- Kiosk Devices
- Shared Workstations

Configure device targeting:

  1. Click Device conditions
  2. Select Device compliance state
  3. Choose Compliant devices only
  4. Add device platform filter: Windows

Set up conditional access integration:

{
  "deviceFilter": {
    "mode": "include",
    "rule": "device.deviceOwnership -eq \"Company\""
  },
  "locations": {
    "includeLocations": ["All"],
    "excludeLocations": ["AllTrustedLocations"]
  }
}
Pro tip: Start with a pilot group of 10-20 users to test the policy before rolling out organization-wide. This helps identify any unexpected blocking issues.

Verification: Click Review + Save and confirm the assignment summary shows your intended user/device scope. The policy should deploy within 15-30 minutes.

04

Create Complementary Intune Settings Catalog Policy for Edge

While Entra Internet Access provides the primary blocking mechanism, you should also configure browser-specific policies through Intune to ensure comprehensive coverage, especially for Microsoft Edge.

Navigate to the Microsoft Intune admin center:

https://endpoint.microsoft.com

Create a new configuration profile:

  1. Go to Devices > Configuration
  2. Click Create > New policy
  3. Platform: Windows 10 and later
  4. Profile type: Settings catalog
  5. Name: Edge - Block Store Web Installer URLs

Configure the Edge URL blocking settings:

  1. Click Add settings
  2. Search for: Microsoft Edge
  3. Expand Microsoft Edge category
  4. Select Block access to a list of URLs

Add the blocked URLs in the value field:

apps.microsoft.com/*
get.microsoft.com/*
store.rg-adguard.net/*
microsoft.com/store/apps/*

Configure additional Edge security settings:

  1. Add Block external extensions (prevents Store extension installs)
  2. Add Control where developer tools can be used > Set to Don't allow using the developer tools
Warning: Test these Edge policies carefully as overly restrictive settings can break legitimate business applications that rely on Edge WebView2 components.

Verification: Assign the policy to the same groups as your Entra policy. Check deployment status in Devices > Monitor > Device configuration.

05

Configure AppLocker Rules for Additional Protection

To prevent users from running downloaded Store installers even if they bypass the web filtering, configure AppLocker rules through Intune to block execution of Store installer files.

In the Intune admin center, create an AppLocker policy:

  1. Go to Endpoint security > Application control
  2. Click Create policy
  3. Platform: Windows 10 and later
  4. Profile: App and browser isolation

Configure the AppLocker XML policy:

<AppLockerPolicy Version="1">
  <RuleCollection Type="Exe" EnforcementMode="Enabled">
    <FilePathRule Id="fd686d83-a829-4351-8ff4-27c7de5755d2" Name="Block Store Installers" Description="Block Microsoft Store web installer executables" UserOrGroupSid="S-1-1-0" Action="Deny">
      <Conditions>
        <FilePathCondition Path="%TEMP%\*.appx" />
        <FilePathCondition Path="%TEMP%\*.msix" />
        <FilePathCondition Path="%DOWNLOADS%\*.appx" />
        <FilePathCondition Path="%DOWNLOADS%\*.msix" />
      </Conditions>
    </FilePathRule>
    <FilePathRule Id="921cc481-6e17-4653-8f75-050b80acca20" Name="Allow System Files" Description="Allow system executables" UserOrGroupSid="S-1-1-0" Action="Allow">
      <Conditions>
        <FilePathCondition Path="%SYSTEM32%\*" />
        <FilePathCondition Path="%PROGRAMFILES%\*" />
      </Conditions>
    </FilePathRule>
  </RuleCollection>
</AppLockerPolicy>

Alternative method using Settings Catalog:

  1. Create new Settings Catalog policy
  2. Search for AppLocker
  3. Add Application Identity > Executable Rules
  4. Configure deny rules for Store installer file types
Pro tip: Use hash-based rules instead of path-based rules for stronger security. Generate hashes of known Store installer files using Get-FileHash -Algorithm SHA256 in PowerShell.

Verification: Test by attempting to run a downloaded .appx file. The system should display an AppLocker block message. Check AppLocker event logs in Event Viewer under Applications and Services Logs > Microsoft > Windows > AppLocker.

06

Test and Verify the Complete Blocking Solution

Now you need to thoroughly test your blocking configuration to ensure it works as expected while not breaking legitimate functionality.

Perform these verification tests on a target device:

Test 1: Web Browser Blocking

  1. Open Microsoft Edge
  2. Navigate to: https://apps.microsoft.com
  3. Expected result: Block page with your custom message
  4. Try: https://get.microsoft.com
  5. Expected result: Same block page

Test 2: Direct App Links

# Test these URLs in Edge:
https://apps.microsoft.com/detail/9NBLGGH4MSV6
https://www.microsoft.com/store/apps/9WZDNCRFJ3Q2
https://get.microsoft.com/installer/download/9NBLGGH4MSV6

Test 3: Verify Store App Updates Still Work

  1. Open Microsoft Store app (Start > Microsoft Store)
  2. Click your profile icon > Downloads and updates
  3. Click Get updates
  4. Verify updates download and install normally

Test 4: Check Policy Application Status

Run these PowerShell commands on the test device:

# Check Intune policy sync status
Get-MpComputerStatus | Select-Object AMEngineVersion, AMProductVersion

# Verify AppLocker policy
Get-AppLockerPolicy -Effective | Select-Object -ExpandProperty RuleCollections

# Check Edge policy application
Get-ItemProperty "HKLM:\SOFTWARE\Policies\Microsoft\Edge" -Name URLBlocklist
Warning: If Store updates fail during testing, immediately check if your URL patterns are too broad. Store updates use different endpoints than web installer downloads.

Verification: Document successful blocks in a test log. Ensure legitimate Microsoft services (Office 365, Teams, Windows Update) continue working normally. If any issues arise, refine your URL patterns to be more specific.

07

Monitor and Maintain the Blocking Policies

After deployment, you need to establish ongoing monitoring to ensure the policies remain effective and don't cause unintended issues.

Set up monitoring in Entra Internet Access:

  1. Go to Protection > Internet Access > Monitoring
  2. Click Web content filtering logs
  3. Configure log retention: 90 days
  4. Enable alerts for policy violations

Create monitoring queries for blocked attempts:

// KQL query for Entra Internet Access logs
InternetAccessLogs
| where TimeGenerated > ago(7d)
| where Action == "Block"
| where DestinationUrl contains "apps.microsoft.com" or DestinationUrl contains "get.microsoft.com"
| summarize BlockCount = count() by UserPrincipalName, DestinationUrl
| order by BlockCount desc

Set up Intune compliance monitoring:

  1. Navigate to Reports > Device compliance
  2. Create custom report for AppLocker violations
  3. Schedule weekly email reports to security team

Configure automated remediation:

# PowerShell script for automated policy health check
$PolicyName = "Block Microsoft Store Web Installer"
$Policy = Get-MgDeviceManagementDeviceConfiguration | Where-Object {$_.DisplayName -eq $PolicyName}

if ($Policy.State -ne "Enabled") {
    Write-Warning "Policy $PolicyName is not enabled!"
    # Send alert to security team
    Send-MailMessage -To "security@company.com" -Subject "Store Blocking Policy Alert" -Body "Policy requires attention"
}

Regular maintenance tasks:

  • Monthly review of blocked URL patterns for new Store installer domains
  • Quarterly testing of policy effectiveness
  • Semi-annual review of user group assignments
  • Annual policy documentation updates
Pro tip: Create a PowerBI dashboard connecting to your Entra logs to visualize blocking trends and identify potential bypass attempts. This helps demonstrate the policy's effectiveness to management.

Verification: Set up a test calendar reminder to verify policies monthly. Check that monitoring dashboards show expected blocking activity and no false positives affecting business applications.

Frequently Asked Questions

Does blocking Microsoft Store web installer affect Windows Store app updates?+
No, blocking the web installer through apps.microsoft.com and get.microsoft.com does not affect Store app updates. App updates use different Microsoft endpoints and occur through the Microsoft Store application or Windows Update services. The web installer blocking specifically targets manual app downloads through browsers while preserving automatic update functionality for already-installed applications.
Can users bypass Entra Internet Access blocking using different browsers?+
Users might attempt to use non-Edge browsers, but you can extend the blocking by deploying browser-specific policies through Intune. For Chrome, use the Chrome Enterprise policy for URL blocking. For Firefox, deploy the Firefox ADMX templates through Group Policy. However, Entra Internet Access provides network-level blocking that should affect all browsers when properly configured with device-based conditional access.
What happens if I accidentally block too many Microsoft domains?+
Overly broad blocking patterns like *.microsoft.com can break essential services including Office 365, Teams, Windows Update, and Intune management. If this occurs, immediately edit your Entra Internet Access policy to use specific paths like apps.microsoft.com/* instead of broad domain wildcards. Always test policies with a pilot group before organization-wide deployment to identify such issues early.
How do I allow specific users to access the Microsoft Store web installer?+
In your Entra Internet Access policy assignments, create an exclusion group for users who need access (typically IT administrators or developers). Add these users to the exclusion group in the policy assignment settings. Alternatively, create a separate conditional access policy that allows Store web installer access for specific security groups while maintaining the block for standard users.
Does this blocking method work on Windows 10 Pro editions without Enterprise features?+
Yes, Entra Internet Access web content filtering works on Windows 10/11 Pro editions as long as the devices are enrolled in Intune and you have the appropriate Entra ID P1 licensing. However, some AppLocker features may be limited on Pro editions. You can use Intune's Settings Catalog to deploy AppLocker policies via CSP even on Pro editions, providing similar functionality to Enterprise AppLocker Group Policy management.

Discussion

Share your thoughts and insights

Sign in to join the discussion