All four List policy endpoints now accept filters. Every policy type filters by name, id, mode, user, userEmail, userGroup and deviceGroup, and each adds its own, such as control, application and logLevel. Repeat a parameter to pass several values.
Pre-login rules are now configurable through the API; the management console has always had them. Set authenticationState to unauthenticated and the rule applies to anonymous Extension users until they authenticate. It must be unscoped, allow or block, and target SaaS applications or groups.
Two new Access and Data login controls. socialLogin blocks consumer social logins (Google, Microsoft, Facebook, GitHub, X, LinkedIn, Apple), with googleAllowedDomains and mfaRequired. idpLogin allows or blocks SSO and SAML logins, globally or per provider domain.
New Customization control sidebar: turn the browser sidebar on or off and publish up to 12 managed shortcuts, each with a name, URL, optional icon and side-view option.
The access control accepts a new webpageFrame object that draws a colored frame with optional text around the page, to mark a regulated environment. Include it to enable the frame, omit it to disable.
The redirect access action is now configurable through the API. Set enforceRedirect.url, add autoRedirect to send the user on without a click, and use enforceRedirectDialogText for the transition page.
Access and Data logging adds dataSnippet and evidenceStorage for content-scanning snippets and scan evidence. Both need logLevel of on or enhanced and a data profile in dlpProfileId.
Applications now carry a classification: Sanctioned, Tolerated, Unsanctioned or Unclassified, and reads return the custom tags that tagIDs sets. Assign tags in the management console for now: it does not surface the IDs these fields expect. Non-web applications also accept an address.
New application type localdesktopcatalog for catalog-based local desktop applications, alongside the admin-defined localdesktopcustom. Both report their executables, so handle the new value if you switch on type.
New read-only IDP Application Sync endpoints. List your providers or fetch one by ID for its displayName, type (currently entraId), live status, and for Entra its tenantId and clientId.
Pending changes can now be filtered by entityTypes, repeatable for several, and by lastUpdatedBy (admin email or service account). lastUpdatedBy=me resolves to the calling identity.
Cloud storage now tells you why a call failed. Create returns 409 when a provider already exists, create and replace return 422 when the request cannot be applied, and delete returns 409 with PROVIDER_IN_USE.
The allowProtectedBetweenRuleApps upload action on File Protection is now writable, not read-only. It lets users upload Prisma-protected files downloaded from the same rule's applications, and still requires fileDownload.action of useInPrismaBrowserOnly.
durationMinutes now applies beyond admin approvals. On the login controls (formLogin, idpLogin, socialLogin, passkeyLogin) it is accepted for every mode except none and also sets how long a user's own bypass lasts, from 10 minutes to 90 days.
Publishing a draft now tells you which 409 you hit through error.code: CONFLICT when the draft has no changes, or PUBLISH_IN_PROGRESS when another publish or reset holds the lock, in which case nothing was published.
Much higher list limits. An application's URL list is no longer capped at 100: it is configurable per tenant up to 15,000 URLs, including the add and remove lists. AWS tenant restrictions take 35,000 account IDs and managedShortcuts 200 entries.
Smaller input changes. sessionRecording is now optional in an Access and Data rule's tracking object and defaults to false, protocolSchemes accepts a bare scheme such as zoom, and microsoftOutlook joins Open Links in External Apps.
Endpoint titles were rewritten to a consistent, action-first style, so Retrieve the Security Policy is now Get the Security policy. Paths, operations and payloads are unchanged, and the reference navigation is now 15 sections.