Good morning everybody I have created a custom Intune policy to push a VPN profile for AzureVPN to my clients that includes the following OMA-URI: OMA-URI - ./User/Vendor/MSFT/VPNv2/test-c1-vnet-core/ProfileXML Data type: String (XML file) XML was downloaded from the Azure Virtual Gateway Point-2-Site Page and works if I import it manually into the AzureVPN Client. But my clients keep getting the following errors in Intune: <a href="https://filestore.community.support.microsoft.com/api/images/e1fd42ff-280c-4558-8d8a-eb9b3d08bc2d?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSRbdJ45s%2FwDKAKdlaq7%2BYdWz1UZ1Stbt6l5Y3FURsXCZg53ru1co3x2Ls5xc6eNo2M5x0h3Hdtj5UraYswGgls3PbIZdbhY4%2B%2BOtrDy1JoPezgSdKi4x%2BbKb3USnBqxA0NgBMxIFLJxxcdCRDfjHiQL7PTwSXxK6gJR8zvi1qYBRnThO0wk0%2Bvdct1IGnusRCj9V9c7Di42mxHh628uGp%2BMojmXTisCBY2lQH24Y4lfbeRhy%2BWL28F%2FCkSnkTPv3uuitEiHNxujq88Drt88%2BI652Req8AqElDQm2mX6q%2FeBY%3D%22filestore.community.support.microsoft.com%22" rel="ugc nofollow"><img src="https://filestore.community.support.microsoft.com/api/images/e1fd42ff-280c-4558-8d8a-eb9b3d08bc2d?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSRbdJ45s%2FwDKAKdlaq7%2BYdWz1UZ1Stbt6l5Y3FURsXCZg53ru1co3x2Ls5xc6eNo2M5x0h3Hdtj5UraYswGgls3PbIZdbhY4%2B%2BOtrDy1JoPezgSdKi4x%2BbKb3USnBqxA0NgBMxIFLJxxcdCRDfjHiQL7PTwSXxK6gJR8zvi1qYBRnThO0wk0%2Bvdct1IGnusRCj9V9c7Di42mxHh628uGp%2BMojmXTisCBY2lQH24Y4lfbeRhy%2BWL28F%2FCkSnkTPv3uuitEiHNxujq88Drt88%2BI652Req8AqElDQm2mX6q%2FeBY%3D" alt="Image" /> And in the event viewer on the affected devices: windows was unable to parse the requested xml data There was no VPN Profile deployed before, is anyone familiar on how to resolve this issue? Any help is greatly appreciated.

Hello, Thank you for posting in Q&A forum. To further troubleshoot this issue, please kindly try below steps: 1.Use an XML validator to verify if there's anything wrong with XML Format. 2.Check Event Logs and see if there's any insights. 3.Make sure that your Windows 11 OS is up to date. I hope the information above is helpful. If you have any questions or concerns, please feel free to let us know. Best regards， Jill Zhou If the Answer is helpful, please click "Accept Answer" and upvote it.

AzureVPN Profile Issue "windows was unable to parse the requested xml data"

Michèle Merlo 5

Good morning everybody

I have created a custom Intune policy to push a VPN profile for AzureVPN to my clients that includes the following OMA-URI:

OMA-URI - ./User/Vendor/MSFT/VPNv2/test-c1-vnet-core/ProfileXML

Data type: String (XML file)

XML was downloaded from the Azure Virtual Gateway Point-2-Site Page and works if I import it manually into the AzureVPN Client.

But my clients keep getting the following errors in Intune:

And in the event viewer on the affected devices:

windows was unable to parse the requested xml data

There was no VPN Profile deployed before, is anyone familiar on how to resolve this issue?

Any help is greatly appreciated.

1 answer

Jing Zhou 7,750 Reputation points Microsoft Vendor

2024-10-31T01:46:22.2633333+00:00

Hello,

Thank you for posting in Q&A forum.

To further troubleshoot this issue, please kindly try below steps:

1.Use an XML validator to verify if there's anything wrong with XML Format.

2.Check Event Logs and see if there's any insights.

3.Make sure that your Windows 11 OS is up to date.

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

Best regards，

Jill Zhou

If the Answer is helpful, please click "Accept Answer" and upvote it.
Please sign in to rate this answer.
Michèle Merlo 5 Reputation points

2024-11-01T16:01:09.56+00:00

Good afternoon

Thanks for your reply, i have this error in my event viewer:

MDM ConfigurationManager: Command failure status. Configuration Source ID: (VVVVVVV-YYYY-XXXX-YYYY-XXXX), Enrollment Name: (MDMDeviceWithAAD), Provider Name: (Policy), Command Type: (Add: from Replace or Add), CSP URI: (./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Receiver/Properties/Policy/FakePolicy/Version), Result: (The system cannot find the file specified.).

The XML was successfully validated and the OS is up to date.

Any more suggestions are much appreciated, have a great weekend!

Michèle Merlo 5 Reputation points

2024-11-04T14:06:31.5166667+00:00

Any updates?

Patrick Baird 0 Reputation points

2024-11-27T15:33:49.2233333+00:00

We've recently run into the same issue. I see the same MDM ConfigurationManager in the eventvwr you mention - from research it says that can be safely ignored. Anyway, here is the one related to this we get. This started after adding a second profile that uses a vWan svhub as the P2S instead of the older VNG solution.

MDM ConfigurationManager: Command failure status. Configuration Source ID: (67F09CAF-3CB5-4DB4-9DBC-A81F853FD1D0), Enrollment Name: (MDMDeviceWithAAD), Provider Name: (VPNv2), Command Type: (Add: from Replace or Add), CSP URI: (./User/Vendor/MSFT/VPNv2/my-apvpn-name/ProfileXML), Result: (Windows was unable to parse the requested XML data.).

XML validates and importing manually always works. I've tried everything I can think of - change the name to shorter, removing the dash, changing <version> to 2 or 1, change between <Vpnprofile> and <AzVpnProfile> tags in combination with the version.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

AzureVPN Profile Issue "windows was unable to parse the requested xml data"

1 answer

Your answer