Share via

Microsoft Intune custom configuration profile for corporate proxy settings reporting failure status code 0x87d101f4

Oluver Koskinen 0 Reputation points
2026-06-10T12:47:10.3+00:00

Hi guys, I created an Intune device configuration asset to enforce a specific proxy server configuration auto-config script (.pac) path layout for all remote business devices. The client devices download the configuration profile but report failure status 0x87d101f4 in the Intune dashboard monitor.

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Domic Vo 24,210 Reputation points Independent Advisor
    2026-06-10T13:43:09.8933333+00:00

    Hi Oluver Koskinen,

    Transitioning from custom OMA-URI settings to the Settings Catalog is the correct approach to ensure stability and compatibility with the NetworkProxy Configuration Service Provider. The identification of GPO conflicts is a common root cause for remediation failures and remains a necessary verification step. By ensuring that no legacy policies exist within the specified registry hive, you allow the MDM channel to successfully establish control over the proxy configuration. Confirming that the PAC file URL is reachable across all network states, especially for remote devices, is essential to prevent sync errors during policy application. Following this transition and clearing legacy precedence should resolve the 0x87d101f4 status error.

    Domic V

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-06-10T12:47:26.1166667+00:00

    Status code 0x87d101f4 isn’t defined in the provided context, but the scenario matches a configuration/profile deployment failure for Windows proxy settings. To successfully enforce a corporate proxy PAC script with Intune, configure and deploy a supported Windows device configuration profile using the built‑in Network proxy settings rather than an incorrect or unsupported custom configuration.

    Use these steps and checks:

    1. Create a supported Windows configuration profile
      1. In Intune admin center, go to Devices.
      2. Under Manage devices, select Configuration > Create > New policy.
      3. Choose Platform = Windows 10 and later.
      4. Choose a profile type that exposes Network proxy (for example, a template that includes Windows device restrictions or the Settings catalog where NetworkProxy CSP is available).
    2. Configure Network proxy settings correctly Using the Network proxy section (which uses the NetworkProxy policy CSP):
      • Automatically detect proxy settings: set to Block if automatic detection must be disabled. Note that when set to Block, the ProxySettingsPerUser setting is automatically set to 0.
      • Use proxy script: set to Allow.
      • Setup script address URL: enter the full URL to the PAC file, for example http://proxy.contoso.com/proxy.pac.
      • If using a manual proxy instead of PAC:
        • Use manual proxy server: set to Allow.
        • Address: enter the proxy host name or IP.
        • Port number: enter the TCP port.
        • Proxy exceptions: list any destinations that must bypass the proxy, separated by semicolons (;).
        • Bypass proxy server for local address: set to Allow if intranet traffic must not use the proxy.
      Ensure the PAC URL is reachable from the client devices and uses a protocol and path supported by the NetworkProxy CSP.
    3. Re‑assign and monitor the profile
      1. Assign the profile to the appropriate device or user groups.
      2. In Devices > Monitor, review configuration policy status and confirm that the new profile shows Succeeded on targeted devices.
    4. If failures persist
      • Confirm that the profile type and settings are supported for the Windows edition in use (as listed in the NetworkProxy policy CSP documentation referenced by the Intune UI).
      • Remove conflicting proxy policies (for example, older device restriction profiles or GPOs) that might cause remediation failures.

    Using the built‑in Network proxy settings in a supported Windows configuration profile and a valid PAC URL aligns with the documented Intune and CSP behavior and should resolve the deployment failures.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.