Merge pull request #292301 from MicrosoftDocs/main

Publish to live, Sunday 4AM PST, 12/22
changeworld · Dec 22, 2024 · a7576bb · a7576bb
2 parents 7aab186 + b654ced
commit a7576bb
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 13 deletions.
diff --git a/articles/cdn/edgio-retirement-faq.md b/articles/cdn/edgio-retirement-faq.md
@@ -6,7 +6,7 @@ services: cdn
 author: duongau
 ms.service: azure-cdn
 ms.topic: how-to
-ms.date: 12/20/2024
+ms.date: 12/21/2024
 ms.author: duau
 ---
 
@@ -38,7 +38,6 @@ The following is a recap of the migration options we sent to all users:
 
     > [!IMPORTANT]
     > - If you plan a migration to Akamai or another CDN provider, you will need set a Feature Flag by following these instructions (select the Feature Flag “DoNotForceMigrateEdgioCDNProfiles”) before January 7, 2025. Doing so will prevent Microsoft from migrating you to Azure Front Door (please see below). Note you will have until January 14, 2025 to complete your migration to another CDN, but again Microsoft cannot guarantee your services will be available on the Edgio platform before this date.
-    > - The Azure Marketplace is currently not available for customers in South Korea.
     > - Please be advised we will need to halt all configuration changes to Azure CDN by Edgio profiles starting on January 3, 2025. This means you will not be able update your CDN profile configuration, but your services on Azure CDN from Edgio will still operate until you are migrated or the Edgio platform is shut down on January 15, 2025
 
 - If you have any services running on Azure CDN from Edgio on January 7, 2025 and haven't informed us of your plans (please see above), we'll attempt to migrate your services over to Azure Front Door on January 7, 2025. We'll be performing this migration to Azure Front Door on a “best effort” basis, and doing so might cause issues related to the billing, features, availability, and/or performance you're currently consuming with Azure CDN from Edgio.
@@ -62,21 +61,10 @@ Depending on your workloads, Azure Front Door can be more cost-effective than Az
 
 For any questions regarding billing changes, reach out to our support team or your account team.
 
-### What options do I have with migrating my workloads from Azure CDN from Edgio?
-
-You're encouraged to migrate your workloads to Microsoft's flagship CDN product called Azure Front Door Standard or Premium. Next steps:
-1. Review [Azure Front Door and Azure CDN features](../frontdoor/front-door-cdn-comparison.md) to determine if Azure Front Door is compatible with your workloads.
-2. Understand [Azure Front Door Pricing](https://azure.microsoft.com/pricing/details/frontdoor/).
-3. Follow the [Azure CDN to Azure Front Door migration guide](../frontdoor/migrate-cdn-to-front-door.md). This guide provides detailed instructions on how to set up an Azure Front Door profile, test functionality, and migrate your compatible workloads from Azure CDN from Edgio to Azure Front Door with the help of Azure Traffic Manager.
-
 ### Does Microsoft validate my workloads work on Azure Front Door?
 
 No, you need to determine if Azure Front Door suits your workloads. We recommend setting up a test environment to validate that your services are compatible with Azure Front Door.
 
-### What will happen if I don't take action before January 15, 2025?
-
-If no action is taken before January 15, 2025, Azure CDN from Edgio profiles and associated data will be removed from Edgio systems. It's imperative that users migrate their workloads before this date to avoid any service disruptions and data loss.
-
 ### What will happen after Microsoft migrates my workloads to Azure Front Door on January 7, 2025?
 
 After the migration, you'll receive an email notification confirming whether your workloads have been successfully migrated to Azure Front Door Standard or if the migration was unsuccessful. We're migrating you to Azure Front Door Standard as it may be more cost-effective. If you need the extra features of Azure Front Door Premium, you can [upgrade your service](../frontdoor/tier-upgrade.md).

diff --git a/articles/governance/policy/concepts/policy-for-kubernetes.md b/articles/governance/policy/concepts/policy-for-kubernetes.md
@@ -606,6 +606,12 @@ Finally, to identify the AKS cluster version that you're using, follow the linke
 
 ### Add-on versions available per each AKS cluster version
 
+#### 1.9.1
+Security improvements.
+- Released January 2025
+- Kubernetes 1.27+
+- Gatekeeper 3.17.1
+
 #### 1.8.0
 Policy can now be used to evaluate CONNECT operations, for instance, to deny `exec`s. Note that there is no brownfield compliance available for noncompliant CONNECT operations, so a policy with Audit effect that targets CONNECTs is a no op.