microsoftgraph / microsoftgraph/msgraph-metadata
GET AppLockerFiles not working
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
Trying to list AppLockerFiles (both allow and exempt) from my MDM policy as explained in [0] gives this 400 error message. Initially I thought it was a service issue in my tenant but then I tested on a separate tenant and have exactly the same issue.
Invoke-GraphRequest : GET https://graph.microsoft.com/beta/deviceAppManagement/mdmWindowsInformationProtectionPolicies/REDACTED/protectedAppLockerFiles
HTTP/1.1 400 Bad Request
[...]
{"error":{"code":"No method match route template","message":"No OData route exists that match template ~/singleton/navigation/key/navigation with http verb GET for request /MAMAdmin_2312/MAMAdminFEService/devic
eAppManagement/mdmWindowsInformationProtectionPolicies('REDACTED')/protectedAppLockerFiles.","innerError":{"date":"2023-12-18T13:12:26","request-id":"REDACTED
b946a8","client-request-id":"REDACTED"}}}
[...]
Didn't test it but most likely it's also not possible to create and delete them and the idea would be to if all these actions are working then add support for AppLockerFiles in Microsoft365DSC's IntuneWindowsInformationProtectionPolicyWindows10MdmEnrolled [1].
[0] https://learn.microsoft.com/en-us/graph/api/intune-mam-windowsinformationprotectionapplockerfile-list?view=graph-rest-beta
[1] https://microsoft365dsc.com/resources/intune/IntuneWindowsInformationProtectionPolicyWindows10MdmEnrolled/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the documented GET request for protectedAppLockerFiles using the Microsoft Graph beta endpoint and compare its route with the error response. Then verify whether create and delete operations behave similarly, and review the linked Microsoft365DSC resource to determine the support requirements; done means the AppLockerFiles actions work or their metadata limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100