Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ez-er

Author: halkazwini

articles/azure-netapp-files/azure-netapp-files-delegate-subnet.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 10/09/2024
+ms.date: 11/27/2024
 ms.author: anfdocs
 ---
 # Delegate a subnet to Azure NetApp Files 
@@ -14,7 +14,15 @@ You must delegate a subnet to Azure NetApp Files. When you create a volume, you
 
 ## Considerations
 
-* When creating the delegated subnet for Azure NetApp Files, the size of the subnet matters. A subnet with a /28 network mask provides (only) 11 usable IP addresses, which might be insufficient for certain use cases. In that case, you should plan for a larger delegated subnet. For instance, a subnet with a /26 network mask provides 59 and a /24 network mask provides 251 available IP addresses respectively. You should consider even larger subnets (for example, /23 network mask) in scenarios where application volume group for SAP HANA is used and where many volumes and storage endpoints are anticipated. The network mask of the delegated network can't be changed after the initial creation. Make sure to plan your virtual network (VNet) and delegated subnet sizes consciously. 
+* When creating the delegated subnet for _Azure NetApp Files_, consider the size of the subnet. A subnet with a **/28 network mask** provides only **11 usable IP addresses**, which might be insufficient for certain use cases. Consider creating a larger subnet mask. For example: 
+
+    - A **/26 network mask** provides **59 usable IP addresses**
+    - A **/24 network mask** provides **251 usable IP addresses**
+
+    In scenarios involving high application volume counts such as _SAP HANA_, consider larger subnets, like a **/23 network mask.** Larger subnets are especially beneficial if you expect many volumes and storage endpoints.
+    
+    Once the delegated network is created, its network mask cannot be altered. Thus it's essential to thoughtfully plan your virtual network (VNet) and delegated subnet sizes with an eye toward the future.
+
 * In each VNet, only one subnet can be delegated to Azure NetApp Files.   
    Azure enables you to create multiple delegated subnets in a VNet.  However, any attempts to create a new volume would fail if you use more than one delegated subnet.  
    You can have only a single delegated subnet in a VNet. A NetApp account can deploy volumes into multiple VNets, each having its own delegated subnet.  

articles/data-factory/connector-rest.md

@@ -928,7 +928,7 @@ The backend will automatically get the next URL based on the RFC 5988 style link
 >
 > :::image type="content" source="media/connector-rest/pagination-rule-example-7-disable-rfc5988.png" alt-text="Screenshot showing how to disable R F C 5988 setting for Example 7."::: 
 
-#### Example 8: The next request URL is from the response body when use pagination in mapping data flows
+#### Example 8a: The next request URL is in the response body when using pagination in mapping data flows
 
 This example states how to set the pagination rule and the end condition rule in mapping data flows when the next request URL is from the response body.
 
@@ -952,6 +952,18 @@ But if the value of **@odata.nextLink** in the last response body is equal to th
 
     :::image type="content" source="media/connector-rest/pagination-rule-example-8-end-condition-2.png" alt-text="Screenshot showing setting the end condition rule when the complete key in the response header equals to true indicates the end of pagination."::: 
 
+#### Example 8b: The next request URL is in the response body when using pagination in copy activity
+
+This example demonstrates how to set the pagination rule in a copy activity when the next request URL is contained within the response body.
+
+The response schema is shown below:
+
+:::image type="content" source="media/connector-rest/pagination-rule-example-8-response-schema.png" alt-text="Screenshot showing the response schema of Example 8b."::: 
+
+The pagination rules should be set as shown in the following screenshot:
+
+:::image type="content" source="media/connector-rest/pagination-rule-example-8b.png" alt-text="Screenshot showing how to set the pagination rule for Example 8b."::: 
+
 #### Example 9: The response format is XML and the next request URL is from the response body when use pagination in mapping data flows
 
 This example states how to set the pagination rule in mapping data flows when the response format is XML and the next request URL is from the response body. As shown in the following screenshot, the first URL is *https://\<user\>.dfs.core.windows.NET/bugfix/test/movie_1.xml*

articles/data-factory/media/connector-rest/pagination-rule-example-8b.png

@@ -18,7 +18,7 @@ In the Azure portal, while creating an event subscription, select **Service Bus
 :::image type="content" source="./media/handler-service-bus/queue.png" lightbox="./media/handler-service-bus/queue.png" alt-text="Screenshot showing the configuration of a Service Bus queue handler.":::
 
 > [!NOTE]
-> Session enabled queues are not supported as event handlers for Azure Event Grid events
+> If you are using session enabled queue/topic subscription as the destination, you need to set the session property on the event using Delivery Property with the header name 'SessionId'.
  
 ### Use Azure CLI
 Use the [`az eventgrid event-subscription create`](/cli/azure/eventgrid/event-subscription) command with `--endpoint-type` set to `servicebusqueue` and `--endpoint` set to `/subscriptions/{AZURE SUBSCRIPTION}/resourceGroups/<RESOURCE GROUP NAME>/providers/Microsoft.ServiceBus/namespaces/<NAMESPACE NAME>/queues/<QUEUE NAME>`. Here's an example:

articles/event-grid/handler-service-bus.md

@@ -13,7 +13,7 @@ metadata:
   ms.topic: hub-page
   author: JnHs
   ms.author: jenhayes
-  ms.date: 04/17/2024
+  ms.date: 12/04/2024
   featureFlags:
   - clicktale
 highlightedContent:
@@ -24,17 +24,17 @@ highlightedContent:
       itemType: get-started
       url: /azure/developer/
     # Card
+    - title: Build skills with Microsoft Learn for Azure
+      itemType: learn
+      url: /training/azure    
+    # Card
     - title: Design your app using the Azure Architecture Center
       itemType: architecture
       url: /azure/architecture/
     # Card
-    - title: Prepare your org with the Cloud Adoption Framework
+    - title: Achieve organizational goals with the Cloud Adoption Framework
       itemType: overview
       url: /azure/cloud-adoption-framework/
-    # Card
-    - title: Build your skills with Microsoft Learn training
-      itemType: learn
-      url: /training/browse/?products=azure&resource_type=learning%20path
 
 productDirectory:
   title: Browse Azure products
@@ -64,7 +64,7 @@ productDirectory:
       url: /azure/ai-studio/
     # Card
     - title: Speech
-      summary: Speech to text, text to speech, translation and speaker recognition
+      summary: Speech to text, text to speech, translation, and speaker recognition
       imageSrc: ./media/index/speech.svg
       azureCategories:
         - ai-machine-learning
@@ -196,7 +196,7 @@ productDirectory:
       url: communications-gateway/index.yml
     # Card
     - title: Data Science Virtual Machines
-      summary: Rich pre-configured environment for AI development
+      summary: Rich preconfigured environment for AI development
       imageSrc: ./media/index/virtual-machine.svg
       azureCategories:
         - ai-machine-learning
@@ -351,14 +351,6 @@ productDirectory:
         - iot
       url: logic-apps/index.yml
     # Card
-    - title: API Apps
-      summary: Easily build and consume Cloud APIs
-      imageSrc: ./media/index/api-apps.svg
-      azureCategories:
-        - compute
-        - containers
-        - web
-      url: app-service/index.yml
     # Card
     - title: App Service
       summary: Quickly create powerful cloud apps for web and mobile
@@ -463,7 +455,7 @@ productDirectory:
         - compute
       url: cloud-services-extended-support/index.yml
     # Card
-    - title: Container Instances
+    - title: Azure Container Instances
       summary: Easily run containers on Azure without managing servers
       imageSrc: ./media/index/container-instances.svg
       azureCategories:
@@ -509,15 +501,6 @@ productDirectory:
         - containers
       url: /azure/service-fabric/
     # Card
-    - title: Web Apps
-      summary: Quickly create and deploy mission critical web apps at scale
-      imageSrc: ./media/index/app-service.svg
-      azureCategories:
-        - compute
-        - containers
-        - web
-      url: app-service/index.yml
-    # Card
     - title: Azure Virtual Desktop
       summary: The best virtual desktop experience, delivered on Azure
       imageSrc: ./media/index/virtual-desktop.svg
@@ -541,7 +524,7 @@ productDirectory:
         - containers
       url: /azure/virtual-machines/linux/openshift-get-started
     # Card
-    - title: Container Registry
+    - title: Azure Container Registry
       summary: Store and manage container images across all types of Azure deployments
       imageSrc: ./media/index/container-registry.svg
       azureCategories:
@@ -785,7 +768,7 @@ productDirectory:
       url: managed-grafana/index.yml
     # Card
     - title: GitHub Actions for Azure
-      summary: Build, test and deploy any app from GitHub to Azure
+      summary: Build, test, and deploy any app from GitHub to Azure
       imageSrc: ./media/index/github-actions-icon.svg
       azureCategories:
         - devops
@@ -805,6 +788,7 @@ productDirectory:
       summary: Synchronize on-premises directories and enable single sign-on
       imageSrc: ./media/index/active-directory.svg
       azureCategories:
+        - featured
         - hybrid
         - identity
         - security
@@ -849,7 +833,7 @@ productDirectory:
       url: /azure/azure-local/
     # Card
     - title: Azure Stack Hub
-      summary: Azure Stack Hub is sold as an integrated hardware system, with software pre-installed on validated hardware
+      summary: Azure Stack Hub is sold as an integrated hardware system, with software preinstalled on validated hardware
       imageSrc: ./media/index/stack-hub.svg
       azureCategories:
         - hybrid
@@ -934,7 +918,7 @@ productDirectory:
       url: iot-central/index.yml
     # Card
     - title: Azure IoT Hub
-      summary: Connect, monitor and manage billions of IoT assets
+      summary: Connect, monitor, and manage billions of IoT assets
       imageSrc: ./media/index/iot-hub.svg
       azureCategories:
         - iot
@@ -1614,10 +1598,10 @@ additionalContent:
     - title: Partner solutions
       items:
         # Card
-        - title: Azure Native ISV Services
-          summary: Integrated partner solutions that you can use in Azure to enhance your cloud infrastructure.
-          url: ./partner-solutions/index.yml
-        # Card
         - title: Commercial marketplace
           summary: An online marketplace of applications and services from independent software vendor (ISV) partners.
           url: ./marketplace/index.yml
+        # Card
+        - title: Azure Native ISV Services
+          summary: Integrated partner solutions that you can use in Azure to enhance your cloud infrastructure.
+          url: ./partner-solutions/index.yml

articles/index.yml

@@ -238,7 +238,7 @@ To determine if the **Microsoft ECC Root Certificate Authority 2017** and **Micr
 1. To add a root certificate to the trusted root certificate store in Java, you can use the `keytool` utility. The following example adds the **Microsoft RSA Root Certificate Authority 2017** root certificate:
 
     ```bash
-    keytool -import -file microsoft-ecc-root-ca.crt -alias microsoft-rsa-root-ca -keystore $JAVA_HOME/jre/lib/security/cacerts
+    keytool -import -file microsoft-ecc-root-ca.crt -alias microsoft-ecc-root-ca -keystore $JAVA_HOME/jre/lib/security/cacerts
     keytool -import -file microsoft-rsa-root-ca.crt -alias microsoft-rsa-root-ca -keystore $JAVA_HOME/jre/lib/security/cacerts
     ```