There are different ways to Import ADMX template files into Intune. You can either use OMA-URI method to Import ADMX template files or you can use Import ADMX option recently made available on Microsoft Endpoint manager admin center.
For importing an ADMX template into Intune, you first need to download ADMX and ADML template files from application vendor website. In my case, I downloaded it from Zoom website.
Once you download ADMX template files, you can use below steps to Import ADMX file into Intune.
- Login on Microsoft Intune Admin Center
- Click on Devices -> Configuration profiles
- Click on Import ADMX
- Click on +Import
On the next screen, you can browse to ADMX and ADML template files and Upload it to Intune. This take few seconds to complete. Upload may fail and the status of Upload may show as Upload Failed as shown in below screenshot:
There could be many reasons for Upload process to fail. One of which could be if you reach maximum limit of the ADMX template files upload. As of now the maximum limit of admx files you can import is 10. If you have not yet reached the limit and getting a different error then you can find it by clicking on Upload Failed Link.
In my case, I was Importing first admx file into intune so I can rule out the issue due to maximum limit. When clicking on Upload Failed error, I could find below error details:
| Error Details |
|---|
| The upload to this ADMX file has failed. To continue, you will need to delete this upload, address the action in the error details and try again. Error Details: ADMX file referenced not found NamespaceMissing:Microsoft.Policies.Windows. Please upload it first. |
How to fix ADMX file referenced not found NamespaceMissing:Microsoft.Policies.Windows
When you try to upload any admx template file into Intune using Import ADMX option. You need to first find out the dependency of this admx files. For example: When we try to upload Zoom ADMX file, it failed with an error message NamespaceMissing:Microsoft.Policies.Windows. Please upload it first.
Let’s open Zoom ADMX file and check the policyNamespaces section. Here we can see that it requries Microsoft.Policies.Windows namespace along with ZoomMeetings_HKLM admx file.
To be able to successfully upload Zoom Meetings App admx template files, we first need to upload windows.admx template file. Let’s download windows.admx template file and upload it first.
Download windows.admx and windows.adml template files
Please follow below steps to download windows.admx and windows.adml files:
- Download Windows 10 admx template files
- This will download msi installer. Open the Installer and Install admx template files
- Go to C:\Windows\PolicyDefinitions location and search for windows.admx file
- Go to C:\Windows\PolicyDefinitions\en-US location and search for windows.adml file
You will need to Import windows.admx and windows.adml files into Intune first and then try to Import Zoom admx files.
Import windows.admx and windows.adml template files
Please follow below steps to Import windows.admx and windows.adml files into Intune:
- Login on Microsoft Intune Admin Center
- Click on Devices -> Configuration profiles
- Click on Import ADMX
- Click on +Import
Browse to windows.admx and windows.adml files. Click on Next and then click on Create.
Import Zoom Meeting Admx template files into Intune
To Import Zoom meeting app admx template files into intune, you need to follow the same steps as performed for importing windows.admx and windows.adml.
- Login on Microsoft Intune Admin Center
- Click on Devices -> Configuration profiles
- Click on Import ADMX
- Click on +Import
Browser to Zoom meeting app admx and adml files and try to import it. This time it should Import successfully.
Conclusion
This blog post shows how to fix the Namespace missing error while trying to upload / Import admx template files into intune. We have taken an example application zoom for this blog post and showed you how to find the dependencies using the admx files and import it first.
If you are trying to import any other application’s admx file into intune and you receive a similar error, you can follow the steps given in this blog post and take the guidance to fix the issue.