starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #1366] Intune Policies/Templates #752

New issue

Closed

opened 2026-03-02 12:44:55 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 12:44:55 +03:00

Owner

Originally created by @SolutionsIT-General on GitHub (Feb 8, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1366

Description

Running into an issue where I want to either convert an existing policy into a template or I export the JSON and try to manually add it and they get blocked by:

Intune Template Deployment failed: The property value exceeds the maximum allowed size (64KB). If the property value is a string, it is UTF-16 encoded and the maximum number of characters should be 32K or less. RequestId:51bc8936-e002-006b-18f9-3bba75000000 Time:2023-02-08T20:07:44.0677314Z Status: 400 (Bad Request) ErrorCode: PropertyValueTooLarge Content: {"odata.error":{"code":"PropertyValueTooLarge","message":{"lang":"en-US","value":"The property value exceeds the maximum allowed size (64KB). If the property value is a string, it is UTF-16 encoded and the maximum number of characters should be 32K or less.\nRequestId:51bc8936-e002-006b-18f9-3bba75000000\nTime:2023-02-08T20:07:44.0677314Z"}}} Headers: X-Content-Type-Options: REDACTED Cache-Control: no-cache DataServiceVersion: 3.0; Content-Type: application/json;odata=minimalmetadata;streaming=true; charset=utf-8

Now what is interesting is I tried an even larger one and got the same message but the maximum allowed size was now 1 MB.

From what I can see 64KB is incredibly small. Even just a handful of policies seems to exceed that limit

Environment data

Running in our azure tenant. Fully up to date

Originally created by @SolutionsIT-General on GitHub (Feb 8, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1366 ### Description Running into an issue where I want to either convert an existing policy into a template or I export the JSON and try to manually add it and they get blocked by: `Intune Template Deployment failed: The property value exceeds the maximum allowed size (64KB). If the property value is a string, it is UTF-16 encoded and the maximum number of characters should be 32K or less. RequestId:51bc8936-e002-006b-18f9-3bba75000000 Time:2023-02-08T20:07:44.0677314Z Status: 400 (Bad Request) ErrorCode: PropertyValueTooLarge Content: {"odata.error":{"code":"PropertyValueTooLarge","message":{"lang":"en-US","value":"The property value exceeds the maximum allowed size (64KB). If the property value is a string, it is UTF-16 encoded and the maximum number of characters should be 32K or less.\nRequestId:51bc8936-e002-006b-18f9-3bba75000000\nTime:2023-02-08T20:07:44.0677314Z"}}} Headers: X-Content-Type-Options: REDACTED Cache-Control: no-cache DataServiceVersion: 3.0; Content-Type: application/json;odata=minimalmetadata;streaming=true; charset=utf-8` Now what is interesting is I tried an even larger one and got the same message but the maximum allowed size was now 1 MB. From what I can see 64KB is incredibly small. Even just a handful of policies seems to exceed that limit ### Environment data ```PowerShell Running in our azure tenant. Fully up to date ```

kerem

2026-03-02 12:44:55 +03:00

closed this issue
added the
bug

unconfirmed-by-user
labels

kerem commented

2026-03-02 12:44:56 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 8, 2023):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

@github-actions[bot] commented on GitHub (Feb 8, 2023): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.". Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

kerem commented

2026-03-02 12:44:56 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Feb 9, 2023):

Not a bug, Microsoft limitation.

@KelvinTegelaar commented on GitHub (Feb 9, 2023): Not a bug, Microsoft limitation.

kerem commented

2026-03-02 12:44:56 +03:00

Author

Owner

@SolutionsIT-General commented on GitHub (Feb 9, 2023):

Is there any way around it? I was really hoping CIPP would be the answer for deploying our baseline policies. The one policy only has maybe 10 settings and it fails :(

@SolutionsIT-General commented on GitHub (Feb 9, 2023): Is there any way around it? I was really hoping CIPP would be the answer for deploying our baseline policies. The one policy only has maybe 10 settings and it fails :(

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#752

No description provided.

Rows
Columns