From 8ed76e088c334fc324a4c119ee7368b50f2d4711 Mon Sep 17 00:00:00 2001 From: brentschaus-okta Date: Thu, 8 May 2025 10:15:31 -0400 Subject: [PATCH] drops ea tag --- .../docs/guides/device-assurance-policies/main/index.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/packages/@okta/vuepress-site/docs/guides/device-assurance-policies/main/index.md b/packages/@okta/vuepress-site/docs/guides/device-assurance-policies/main/index.md index 026d93013ce..c6eefb6fd56 100644 --- a/packages/@okta/vuepress-site/docs/guides/device-assurance-policies/main/index.md +++ b/packages/@okta/vuepress-site/docs/guides/device-assurance-policies/main/index.md @@ -45,8 +45,6 @@ Use the [Device Assurance Policy API](https://developer.okta.com/docs/api/openap ### About Dynamic OS version compliance - - You can configure OS version compliance by using device assurance. However, you have to manually update the policies every time a new OS version or patch is released. With Dynamic OS version compliance, Okta updates device assurance policies with the latest OS versions and patches, eliminating the need for manual updates. With this feature you can ensure OS version compliance in your org without tracking OS releases. To use Dynamic OS version compliance, you need to define the `dynamicVersionRequirement` object. See [Example POST request](#example-post-request).