By: Wayne Bennett – Sr. Product Manager | Microsoft Intune
Google recently implemented changes in May 2025 which require Android 13 or above devices to need hardware-backed security signals and...
Updated Aug 26, 2025
Version 4.0
Blog Post
5 MIN READ
Support tip: Changes to Google Play strong integrity for Android 13 or above
How do we choose the right date value? Do we have to update it with every new version released, monthly? 🙃
Wayne BennettMicrosoft
Hi carlosbh, we are aware of the fixed date limitation. Unfortunately, at this time you will need to periodically edit the date within the App Protection Policy, there is no "rolling timeframe" setting.
Wayne, your developers cant figure out how to program a "Last Year" var? That's baked into most time functions of most programming languages, and powershell. Let me copilot that for you...
PS:
$lastYearDate = $currentDate.AddYears(-1)
This whole thing is frustrating because nothing actually has to be done unless we want to trigger non-compliance off of "Strong Integrity".
The way this is worded, and what me and my Enterprise Mobility team have been scrambling on the last couple of days, makes it seem that devices will be marked as noncompliant and blocked if we don't do anything by 9/30.... When in reality, devices will ONLY be affected if we make policies to affect them.
It's just another control mechanism for security. I really wish this was clearly stated on all mentions of this change, in the first sentence.
- Wayne Bennett
In response to comments from another contributor, a post was added on the 24th July to clarify that action was only required for existing users/devices which are targeted with a policy requiring Strong Integrity and the 'block' value. However, following your valuable feedback the following has been adding to the 3rd paragraph of this post "if you have existing or plan to create device compliance or APP conditional launch policies with the Check strong integrity value".
