The Content Provider Code behavior now lets you configure the property to use the default CP code. Every contract has its own default CP code, and you can apply it to any of the contract's property configurations.

We're pleased to introduce a new validation capability for Cloud Certificate Manager certificates in Limited Availability. Now you can now select third-party certificates when creating edge hostnames in Property Manager, providing streamlined hostname configuration and simplified certificate workflows integrated with your existing Property Manager properties.

We have introduced a new Google Tag Gateway behavior. It allows you to enable first-party Google script loading by adding the Google Tag IDs for the Ion product.

• New frozen rule format available for Property Manager users: v2025-09-09.
• Now in the Origin Server behavior you can select Akamai Object Storage as an origin type when delivering your content using Property Manager. You can also choose Akamai Object Storage as the authentication method in the Origin Characteristics behavior.
• We enhance the Content Targeting Protection behavior to let you ignore the information from the X-Forwarded-For header for Geo Protection and IP Protection.
• We extend the Allow Delete, Allow PATCH, Allow POST, and Allow PUT behaviors to support Adaptive Media Delivery and Object Delivery.
• The Post Quantum Cryptography to Origin behavior is enhanced with a new PQC Keys in First ClientHello option. It lets you send the hybrid X25519MLKEM768 key in the first ClientHello.
• The adaptiveAcceleration behavior is now enhanced to avoid external resource calls. The source option uses hard-coded enum values, MPULSE and REAL_USER_MONITORING, instead of free-form strings.
• The HTTP/2 Edge to Origin option in the Origin Server behavior is incompatible with the WebSockets behavior. It will use HTTP/1.1 for the Edge to origin connection.

As part of the product life cycle management, the following Akamai Cloud Embed behaviors are decommissioned and no longer available:

We introduce a new Post Quantum Cryptography Client to Edge behavior in Limited Availability. To enable it, contact your Akamai account team. It allows you to enable Post Quantum Cryptography (PQC) key exchanges from Client to Edge. We recommend enabling PQC Client to Edge for enhanced security. You may disable PQC Client to Edge if you observe high latency or increased error rate on your clients.

• We remind you that the Cache HTTP Error Responses behavior works only with the Caching behavior enabled.
• The Scheduled Invalidation behavior is no longer compatible with the Metadata Stage match.
• The hostname buckets are now supported with the Adaptive Media Delivery (AMD) properties. See Add hostnames to the hostname bucket.
• The Image and Video Manager behavior is incompatible with the Client IP criteria.

The Origin Server behavior is enhanced to support the HTTP/2 Edge Server to Origin option. It lets you enable the edge server to send multiple HTTP requests over a single HTTP/2 connection to the origin.

• New frozen rule format available for Property Manager users: v2025-07-07.
• The EdgeWorkers behavior is enhanced with the Continue on error option that allows requests to continue processing to the next step even if an EdgeWorkers event handler fails.
• We remind you that the Quick Retry behavior is not compatible with the Cache Tag behavior. Don't include both behaviors in a rule for the same request.
• The Media Acceleration (QUIC Protocol) Opt-Out and QUIC Support behaviors are deprecated.
• We improved the API error messages and warnings to include clear causes and actionable guidance, which will help you to resolve issues efficiently when using ​Akamai​ products.

We introduce a new Post Quantum Cryptography to Origin behavior in Limited Availability. To enable it, contact your Akamai account team. It allows you to enable Post Quantum Cryptography (PQC) key exchanges with your origin. We recommend enabling PQC for enhanced security, however you can disable PQC if you observe very high TLS handshake latency or if your origin either presents errors with larger PQC Client Hellos or has a faulty PQC implementation.