Friday, 30 January 2026

A quiet documentation day, led by clearer Akamai WAF verification guidance for External ID

The 30 January records contain six documentation updates and no new, removed, preview, generally available, or retired capability. The most consequential change is procedural: the External ID Akamai integration guidance now calls for post-configuration verification that Akamai WAF protects the external tenant. Other substantive items clarify Entra ID licensing and device-identity fields, while Global Secure Access documents where a PowerShell-acquired token is written. The two minimum-license records expose only author metadata and do not support a concrete admin conclusion.

• External ID · Authentication

  External ID: Akamai guidance emphasizes post-configuration WAF verification

  The updated Configure Akamai Integration guidance says that, after configuration, administrators should verify that Akamai WAF is protecting the external tenant by connecting the authentication credentials to the WAF configuration. This is procedural security-validation guidance, not evidence of a new integration capability or availability change.

• Entra ID · General

  Entra ID: P2 offering language clarifies standalone and bundled availability

  The Entra Offerings update states that Microsoft Entra ID P2 is available as a standalone product and is also included with specified enterprise offers. Treat this as licensing documentation clarification; the supplied text does not indicate changed pricing or entitlements.

• Entra ID · Security

  Entra ID: Manage Device Identities documents a broader field set

  The update presents fields including identifiers, account status, operating-system details, trust or join type, MDM, security-management and compliance status, registration and sign-in timestamps, owner, and UPN. It helps administrators interpret or report the documented device attributes, but does not indicate a change to device-management behavior.

• Global Secure Access · General

  Global Secure Access: PowerShell token guidance specifies the output path

  The Powershell Get Token update says that the acquired access token is available in `C:\token.txt`. This is an operational documentation detail for scripts and runbooks; the record does not indicate a change to the token flow or Global Secure Access behavior.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.