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.

• New frozen rule format available for Property Manager users: v2025-05-30.
• The Enhanced Debug behavior is now available by default for all products.
• We update the Enhanced Proxy Detection with GeoGuard behavior to support Relay Proxy and Proxy Over VPN.
• Now the Origin Server behavior supports 9444 as the valid HTTPS port.
• The ESI (Edge Side Includes) and the Akamizer behaviors are not compatible with Resource Optimizer and Brotli Compression for ION products.

• New frozen rule format available for Property Manager users: v2025-04-29.
• The Early Data (0-RTT) Advanced behavior is now enhanced with the Supported HTTP Methods option that lists all HTTP methods supported in Early Data.
• Now you can use variables in the cookie name and the value fields in the Request Cookie behavior.
• We update the HTTP Strict Transport Security (HSTS) behavior to support the ‘2 years’ option in the Max age field.
• We decommission the IBM Tealeaf Connector behavior.
• Now the Origin Server behavior supports 9443 as the valid HTTPS port.

We're pleased to introduce a new validation capability for Default certificates in General Availability. Now you can validate your Default certificates using HTTP and DNS TXT records, bringing additional flexibility to certificate management workflows.

• New frozen rule format available for Property Manager users: v2025-03-24.
• The Cache ID Modification behavior is now available in the Advanced Cache Optimization module for Adaptive Media Delivery, Download Delivery, and Object Delivery. Note that for AMD, Property Manager displays an error when the Cache ID Modification behavior is added and the property is configured with MSL Origin or the property has the Watermarking behavior enabled.
• General Availability release of the mTLS Edge Server to Origin behavior. With this behavior enabled, you can configure your delivery property to establish an mTLS connection between the edge server and the origin to authenticate requests. This ensures that the requests to your origin server come directly from the Akamai network.
• Now the CORS Protocol Support behavior supports also the HEAD method.
• We clarify that the Enforce mTLS settings behavior only checks the Certificate Provisioning System settings. It doesn't check the current client certificate and doesn't deny invalid certs.