Merge pull request #292093 from MicrosoftDocs/main

12/17/2024 PM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -4035,6 +4035,11 @@
       "redirect_url": "/azure/managed-grafana/overview",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/managed-grafana/how-to-create-api-keys.md",
+      "redirect_url": "/azure/managed-grafana/how-to-service-accounts",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/load-balancer/move-across-regions-external-load-balancer-portal.md",
       "redirect_url": "/azure/load-balancer/move-across-regions-azure-load-balancer",

articles/azure-government/documentation-government-csp-list.md

@@ -83,6 +83,7 @@ The following tables contain lists of all the authorized Cloud Solution Provider
 |[CACI Inc - Federal](https://www.caci.com/)|
 |[Caloudi Corporation](https://www.caloudi.com/)|
 |[Cambria Solutions, Inc.](https://www.cambriasolutions.com/)|
+|[CapGemini](https://www.capgemini.com)|
 |[CAPSYS Technologies, LLC](https://www.capsystech.com/)|
 |[Casserly Consulting](https://www.casserlyconsulting.com)|
 |[Carahsoft Technology Corporation](https://www.carahsoft.com/)|
@@ -517,29 +518,29 @@ The following tables contain lists of all the authorized Cloud Solution Provider
 |[Accenture LLP](https://www.accenture.coM)|
 |[Agile IT, Inc](https://www.agileit.com)|
 |[American Technology Services LLC](https://networkats.com)|
-|Applied Information Sciences|
-|[Applied Insight LLC](https://www.applied-insight.com)|
+|[Applied Information Sciences](https://www.ais.com)|
 |[Applied Research Solutions](https://www.appliedres.com)|
 |[Arctic Information Technology, Inc.](https://arcticit.com)|
-|[Booz Allen Hamilton](https://www.boozallen.com/)|
+|[Ardalyst](https://ardalyst.com)|
+|[Ariento](https://ariento.com)|
 |[C3 Integrated Solutions, Inc.](https://www.c3isit.com)|
 |[CACI](https://www.caci.com)|
 |[Carahsoft](https://www.carahsoft.com/microsoft)|
-|[Catapult Systems, LLC](https://www.catapultsystems.com)|
 |[CGI Federal Inc.](https://www.cgi.com/us/en-us/federal)|
+|[Charles IT](https://www.charlesit.com)|
 |[Cloud Navigator, Inc - formerly ISC](https://cloudnav.com)|
 |[CloudFit Software LLC](https://cloudfitsoftware.com/)|
+|[Compunet Inc.](https://vanasolutions.com/)|
 |[Conquest Cyber](https://conquestcyber.com/)|
 |[Coretek](https://www.coretek.com/)|
 |[CyberSheath](https://cybersheath.com)|
 |[Daymark Solutions, Inc.](https://www.daymarksi.com/)|
-|[DLT](https://www.dlt.com/)|
 |[Dox Electornics Inc.](https://www.doxnet.com)|
 |[ECF Data, LLC](https://www.ecfdata.com)|
 |[ECS Federal, LLC](https://ecstech.com/)|
-|[Enlighten IT Consulting](https://www.eitccorp.com/)|
 |[eTrepid Inc.](https://www.etrepid.com/)|
 |[F1 Soluitions Inc](https://www.f1networks.com)|
+|[FCN Inc. ](https://fcnit.com)|
 |[Four Points Technolgy, LLC](https://www.4points.com)|
 |[G2 Ops, Inc.](https://g2-ops.com)|
 |[General Dynamics Information Technology](https://www.gdit.com)|
@@ -550,16 +551,17 @@ The following tables contain lists of all the authorized Cloud Solution Provider
 |[IBM Corp.](https://www.ibm.com/industries/government)|
 |[Jackpine Technologies](https://www.jackpinetech.com)|
 |[Jasper Solutions](https://www.jaspersolutions.com/)|
-|[Johnson Technology Systems Inc](https://www.jtsusa.com/)|
 |[KAMIND IT, Inc.](https://www.kamind.com/)|
 |[KTL Solutions, Inc.](https://www.ktlsolutions.com)|
 |[Leidos](https://www.leidos.com/)|
 |[LiftOff, LLC](https://www.liftoffonline.com)|
+|[MAG Aerospace](https://www.magaero.com)|
 |[ManTech](https://www.mantech.com/)|
 |[NeoSystems LLC](https://www.neosystemscorp.com/solutions-services/microsoft-licenses/microsoft-365-licenses/)|
 |[Nimbus Logic, LLC](https://www.nimbus-logic.com/)|
 |[Northrop Grumman](https://www.northropgrumman.com/)|
 |[Novetta](https://www.novetta.com)|
+|[Orbis](https://orbisops.com)|
 |[PAX 8](https://www.pax8.com)|
 |[Permuta Technologies, Inc.](http://www.permuta.com/)|
 |[Planet Technologies, Inc.](https://go-planet.com)|
@@ -576,8 +578,8 @@ The following tables contain lists of all the authorized Cloud Solution Provider
 |[Summit 7 Systems, Inc.](https://www.summit7.us/)|
 |[SysArc Inc.](https://www.sysarc.com)|
 |[TechTrend, Inc](https://techtrend.us)|
+|[Vana Solutions](https://www.vanasolutions.com)|
 |[VLCM](https://www.vlcmtech.com)|
-|[VC3](https://www.vc3.com)|
 |[Vexcel](https://www.vexcel.com/)|
 
 To learn more about the Cloud Solution Provider program, see [Frequently asked questions for Partner Center](/partner-center/faq-for-us-govt-cloud). If you would like to apply for the program, visit [Azure Government CSP application process](./documentation-government-csp-application.md). For any other questions, contact [Azure Government CSP](mailto:[email protected]).

articles/cdn/edgio-retirement-faq.md

@@ -6,19 +6,23 @@ services: cdn
 author: duongau
 ms.service: azure-cdn
 ms.topic: how-to
-ms.date: 10/30/2024
+ms.date: 12/17/2024
 ms.author: duau
 ---
 
 # Azure CDN from Edgio retirement FAQ
 
-Azure CDN from Edgio will be retired on November 4, 2025. You must migrate your workload to Azure Front Door before this date to avoid service disruption. This article provides answers to common questions about the retirement of Azure CDN from Edgio.
+Azure CDN from Edgio will be retired on January 15, 2025. You must migrate your workload to Azure Front Door before this date to avoid service disruption. This article provides answers to common questions about the retirement of Azure CDN from Edgio.
 
 ## Frequently asked questions
 
+### Why was the retirement date of Azure CDN from Edgio changed from November 4, 2025, to January 15, 2025?
+
+Edgio has informed us that their platform is now scheduled to shut down on January 15, 2025. Therefore, all Azure CDN from Edgio customers must migrate their workloads to Azure Front Door or other CDN services before this date.
+
 ### I see Edgio filed for Chapter 11 bankruptcy. Can Microsoft guarantee that Azure CDN from Edgio’s availability and services until November 4, 2025?
 
-Edgio informed us that their services remain operational until at least November 4, 2025. However, we can't guarantee that Edgio doesn't unexpectedly cease operations before this date due to circumstances beyond our control.
+Edgio informed us that their services remain operational until at least January 15, 2025. However, we can't guarantee that Edgio doesn't unexpectedly cease operations before this date due to circumstances beyond our control.
 
 ### What options do I have with migrating my workloads from Azure CDN from Edgio?
 
@@ -27,6 +31,13 @@ You're encouraged to migrate your workloads to Microsoft's flagship CDN product
 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.
 
+### If I determine my workload isn't a match for Azure Front Door, what are my options?
+
+Consider whether Akamai or another CDN provider might be compatible with your needs. You can explore Akamai options through Azure Marketplace. If you decide to work with Akamai, contact Microsoft Support for assistance, and we can connect you with the Akamai team dedicated to migrations.
+
+> [!NOTE]
+> The Azure Marketplace is currently unavailable for customers in South Korea.
+
 ### If I determined my workload isn't a match for Azure Front Door, what are my options?
 
 If you find that Azure Front Door isn't suitable for your workload, we offer an alternative service called [Routing Preference Unmetered](../virtual-network/ip-services/routing-preference-unmetered.md), also known as "CDN Interconnect." This service might allow free data transfer for traffic egressing from your Azure resources to another CDN of your choice.
@@ -37,10 +48,18 @@ Additionally, you can choose to continue working directly with Edgio to minimize
 
 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 November 4, 2025?
+### What will happen if I don't take action before January 15, 2025?
 
-If no action is taken before November 4, 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.
+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.
 
 ### How is Microsoft communicating the retirement of Azure CDN from Edgio, and how often are reminders sent?
 
 We communicate the retirement of Azure CDN from Edgio through multiple channels, including email notifications and in-portal messages. Reminders are sent at least monthly to all users with active Edgio profiles to ensure they're aware of the upcoming changes and necessary actions.
+
+### When will it no longer be possible to create new Azure CDN from Edgio profiles?
+
+New Azure CDN from Edgio profiles can't be created after December 13, 2025.
+
+### Can I request an extension for the retirement/shutdown of the Azure CDN from Edgio service?
+
+No, extensions aren't possible. Edgio confirmed that their platform will shut down by January 15, 2024.

articles/connectors/connectors-create-api-servicebus.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 10/26/2024
+ms.date: 12/16/2024
 ms.custom: engagement-fy23
 ---
 
@@ -133,11 +133,9 @@ To increase the timeout for sending a message, [add the **ServiceProviders.Servi
   > However, despite this setting, the message still might not complete if your workflow remains in a 
   > throttled state at next polling interval.
   >
-  > However, if you [turn on a Service Bus trigger's concurrency setting](../logic-apps/logic-apps-workflow-actions-triggers.md#change-trigger-concurrency), 
-  > the default value for the `maximumWaitingRuns` property is 10. Based on the Service Bus entity's lock duration setting 
-  > and the run duration for your workflow, this default value might be too large and might cause a "lock lost" exception. 
-  > To find the optimal value for your scenario, start testing with a value of 1 or 2 for the `maximumWaitingRuns` property. 
-  > To change the maximum waiting runs value, review [Change waiting runs limit](../logic-apps/logic-apps-workflow-actions-triggers.md#change-waiting-runs).
+  > If you must change the concurrency on a Service Bus auto-complete trigger, don't make this change before 
+  > you initially save your workflow. Create and save your workflow first before you edit the trigger to change the concurrency.
+    ```
 
 ### Service Bus built-in connector triggers
 

articles/container-apps/custom-domains-certificates.md

@@ -83,14 +83,19 @@ Azure Container Apps allows you to bind one or more custom domains to a containe
 
     # [Private endpoint](#tab/private-endpoint)
 
-    - If you selected *A record*, you need to have a private DNS zone which has the same DNS zone name as your public DNS. Create the following DNS records on your private DNS zone:
-
+    - If you selected *A record*, you need to have a private DNS zone which has the same DNS zone name as your public DNS. Create the following DNS record on your private DNS zone: 
+    
         | Record type | Host | Value |
         |--|--|--|
         | A | `@` | The Private IP of your private endpoint on your container apps environment. |
+
+        In addition, you will need to add the following record to your public DNS zone.
+
+        | Record type | Host | Value |
+        |--|--|--|
         | TXT | `asuid` | The domain verification code. |
 
-    - If you selected *CNAME*, create the following DNS records:
+    - If you selected *CNAME*, create the following DNS records on your public DNS zone:
 
         | Record type | Host | Value |
         |--|--|--|

articles/data-factory/index.yml

@@ -46,6 +46,8 @@ landingContent:
             url: ./concepts-pipeline-execution-triggers.md
           - text: Mapping data flows in Azure Data Factory
             url: ./concepts-data-flow-overview.md
+          - text: Using expressions and functions
+            url: ./control-flow-expression-language-functions.md
       - linkListType: quickstart
         links:
           - text: Create an Azure Data Factory with UI
@@ -68,14 +70,6 @@ landingContent:
             url: ./copy-activity-performance-troubleshooting.md
           - text: Troubleshoot connectors
             url: ./connector-troubleshoot-guide.md
-      - linkListType: tutorial
-        links:
-          - text: Copy data in cloud
-            url: ./tutorial-copy-data-tool.md
-          - text: Copy data in bulk
-            url: ./tutorial-bulk-copy-portal.md
-          - text: Copy data incrementally
-            url: ./tutorial-incremental-copy-overview.md
   - title: Data transformation
     linkLists:
       - linkListType: tutorial
@@ -84,10 +78,22 @@ landingContent:
             url: ./data-flow-create.md
           - text: Copy and transform data from a REST endpoint
             url: ./connector-rest.md
+  - title: Lift and shift SSIS packages
+    linkLists:
+      - linkListType: overview
+        links:
+          - text: SSIS migration assessment rules
+            url: ./scenario-ssis-migration-rules.md
       - linkListType: concept
         links:
-          - text: Change Data Capture (CDC)
-            url: ./concepts-change-data-capture.md
+          - text: Integration runtime in Azure Data Factory
+            url: ./concepts-integration-runtime.md
+          - text: Create a self-hosted integration runtime
+            url: ./create-self-hosted-integration-runtime.md
+      - linkListType: tutorial
+        links:
+          - text: Running SSIS packages in Azure
+            url: ./tutorial-deploy-ssis-packages-azure.md            
   - title: Workflow Orchestration Manager
     linkLists:
       - linkListType: concept
@@ -124,20 +130,6 @@ landingContent:
             url: industry-sap-templates.md
           - text: SAP change data capture (CDC) capabilities
             url: sap-change-data-capture-introduction-architecture.md
-  - title: Lift and shift SSIS packages
-    linkLists:
-      - linkListType: overview
-        links:
-          - text: SSIS migration assessment rules
-            url: ./scenario-ssis-migration-rules.md
-      - linkListType: concept
-        links:
-          - text: Integration runtime in Azure Data Factory
-            url: ./concepts-integration-runtime.md
-      - linkListType: tutorial
-        links:
-          - text: Running SSIS packages in Azure
-            url: ./tutorial-deploy-ssis-packages-azure.md
   - title: Author, Monitor and Manage
     linkLists:
       - linkListType: how-to-guide

articles/dev-box/how-to-configure-azure-compute-gallery.md

@@ -52,8 +52,7 @@ The image version must meet the following requirements:
 - Generation 2
 - Hyper-V v2
 - Windows OS
-    - Windows 10 Enterprise version 20H2 or later
-    - Windows 11 Enterprise 21H2 or later
+    - Supported versions of [Windows 10 or Windows 11 Enterprise](/windows/release-health/supported-versions-windows-client).
 - Generalized VM image
     - For more information about creating a generalized image, see [Reduce provisioning and startup times](#reduce-provisioning-and-startup-times) for more information.
 - Single-session VM image (Multiple-session VM images aren't supported.)

articles/firewall/roles-permissions.md

@@ -0,0 +1,65 @@
+---
+title: About Azure Firewall roles and permissions
+titleSuffix: Azure Firewall
+description: Learn about roles and permissions for Azure Firewall.
+author: raboilla
+ms.service: azure-firewall
+ms.topic: conceptual
+ms.date: 12/9/2024
+ms.author: victorh
+
+---
+# About roles and permissions for Azure Firewall
+
+The Azure Firewall utilizes multiple resources, such as virtual networks and IP addresses, during both creation and management operations.
+Because of this, it's essential to verify permissions on all involved resources during these operations.
+
+## Azure built-in roles
+
+You can choose to assign [Azure built-in roles](../role-based-access-control/built-in-roles.md) to a user, group, service principal, or managed identity such as [Network contributor](../role-based-access-control/built-in-roles.md#network-contributor), which support all the required permissions for creating the gateway.
+For more information, see [Steps to assign an Azure role](../role-based-access-control/role-assignments-steps.md).
+
+## Custom roles
+
+If the [Azure built-in roles](../role-based-access-control/built-in-roles.md) don't meet the specific needs of your organization, you can create your own custom roles.
+Just like built-in roles, you can assign custom roles to users, groups, and service principals at management group, subscription, and resource group scopes.
+For more information, see [Steps to create a custom role](../role-based-access-control/custom-roles.md#steps-to-create-a-custom-role)  .
+
+To ensure proper functionality, check your custom role permissions to confirm user service principals, and managed identities operating the Azure Firewall have the necessary permissions.
+To add any missing permissions listed here, see [Update a custom role](../role-based-access-control/custom-roles-portal.md#update-a-custom-role).
+
+## Permissions
+
+Depending on whether you're creating new resources or using existing ones, add the appropriate permissions from the following list for Azure Firewall in a Hub VNET:
+
+|Resource | Resource status | Required Azure permissions |
+|---|---|---|
+| Subnet | Create new| Microsoft.Network/virtualNetworks/subnets/write<br>Microsoft.Network/virtualNetworks/subnets/join/action |
+| Subnet | Use existing| Microsoft.Network/virtualNetworks/subnets/read<br>Microsoft.Network/virtualNetworks/subnets/join/action |
+| IP addresses| Create new| Microsoft.Network/publicIPAddresses/write<br>Microsoft.Network/publicIPAddresses/join/action |
+| IP addresses  | Use existing| Microsoft.Network/publicIPAddresses/read<br>Microsoft.Network/publicIPAddresses/join/action |
+
+If you are creating an Azure Firewall in Azure Virtual WAN, add the following permission:
+
+|Resource | Resource status | Required Azure permissions |
+|---|---|---|
+| virtualHubs | Create new | Microsoft.Network/virtualHubs/read
+
+For more information, see [Azure permissions for Networking](../role-based-access-control/permissions/networking.md) and [Virtual network permissions](../virtual-network/virtual-network-manage-subnet.md#permissions).
+
+## Roles scope
+
+In the process of custom role definition, you can specify a role assignment scope at four levels: management group, subscription, resource group, and resources. To grant access, you assign roles to users, groups, service principals, or managed identities at a particular scope.
+
+These scopes are structured in a parent-child relationship, with each level of hierarchy making the scope more specific. You can assign roles at any of these levels of scope, and the level you select determines how widely the role is applied.
+
+For example, a role assigned at the subscription level can cascade down to all resources within that subscription, while a role assigned at the resource group level will only apply to resources within that specific group. Learn more about scope level
+For more information, see [Scope levels](../role-based-access-control/scope-overview.md#scope-levels).
+
+> [!NOTE]
+> Allow sufficient time for [Azure Resource Manager cache](../role-based-access-control/troubleshooting.md) to refresh after role assignment changes.
+
+## Next steps
+
+[What is Azure Role Based Access](../role-based-access-control/overview.md)
+[Azure Role Based Access Control](../role-based-access-control/role-assignments-list-portal.yml)

articles/firewall/toc.yml

@@ -91,6 +91,8 @@ items:
         href: policy-rule-sets.md
       - name: Policy Analytics
         href: policy-analytics.md
+    - name: Roles and permissions
+      href: roles-permissions.md  
     - name: Azure Firewall web categories
       href: web-categories.md
     - name: Infrastructure FQDNs