Licensing Governance
Updated|[Automated provisioning to on-premises apps](~/identity/app-provisioning/on-premises-application-provisioning-architecture.md)|| :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
Daily.Entra.NewsThe 19 December period is documentation-maintenance heavy: all seven supplied records are updates, with no new or removed items and no Message Center entries. The clearest change is a scope clarification for Microsoft Entra app-gallery OIDC configuration, while Global Secure Access updates spell out administrator sign-in and web-content-check procedures. The evidence does not show a new feature, changed runtime behavior, general availability announcement, retirement, or security advisory. Although an updated page is titled “What is application usage analytics? (preview),” its supplied snippet contains only an author metadata line and does not establish a preview rollout or capability change.
The updated “Configure an OpenID Connect OAuth application from Microsoft Entra app gallery” article says it focuses on gallery applications that implement OIDC and directs readers to separate guidance for in-house or other custom applications. This is a documentation-scope clarification, not evidence of a new OIDC capability or availability change.
The updated Secure Web AI Gateway Agents procedure explicitly instructs operators to sign in to the Microsoft Entra admin center as a Global Secure Access Administrator. The supplied text supports a procedural clarification, but does not establish a new role, permission-model change, or feature rollout.
The Check Web Content Filtering Categories procedure spells out the request format and tells readers to replace example.com with the host or path being checked, using msn.com/en-us/sports as an example. This clarifies request construction; no change to filtering categories or enforcement behavior is shown.
The updated Licensing Governance page displays a matrix entry for “Automated provisioning to on-premises apps” with checkmarks across the excerpted columns. Because the supplied text omits the column headers and the meaning of the marks, it cannot support a conclusion that license entitlements or pricing changed.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
|[Automated provisioning to on-premises apps](~/identity/app-provisioning/on-premises-application-provisioning-architecture.md)|| :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
| Metadata value | Value | Comments |
1. Create or modify an existing policy.
This article focuses on applications in the application gallery that implement OpenID Connect. For more information on enabling OpenID Connect for other applications, including in-house developed applications, see [OpenID Connect on the Microsoft identity platform](~/identity-platform/v2-protocols-oidc.md) and [Configure OIDC SSO for custom (non-gallery) applications](~/identity/enterprise-apps/add-application-portal-setup-oidc-sso.md?#configure-oidc-sso-for-custom-non-gallery-applications).
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as a [Global Secure Access Administrator](../identity/role-based-access-control/permissions-reference.md#global-secure-access-administrator).
3. Use the following request format, replacing example.com with the host/path you want to check (for example, `msn.com/en-us/sports`):
manager: dougeby