Merge branch 'MicrosoftDocs:main' into main

Author: riperez123

articles/azure-netapp-files/data-protection-disaster-recovery-options.md

@@ -47,7 +47,7 @@ Using snapshot technology, you can replicate your Azure NetApp Files across desi
 - Data availability and redundancy for remote data processing and user access 
 - Efficient storage-based data replication without load on compute infrastructure 
 
-To learn more, see [How volumes and snapshots are replicated cross-region for DR](snapshots-introduction.md#how-volumes-and-snapshots-are-replicated-cross-region-for-disaster-recovery-and-business-continuity). To get started with cross-region replication, see [Create cross-region replication for Azure NetApp Files](cross-region-replication-create-peering.md). 
+To learn more, see [How volumes and snapshots are replicated cross-region for DR](snapshots-introduction.md#how-volumes-and-snapshots-are-replicated-for-disaster-recovery-and-business-continuity). To get started with cross-region replication, see [Create cross-region replication for Azure NetApp Files](cross-region-replication-create-peering.md). 
 
 ## Cross-zone replication 
 

articles/azure-netapp-files/manage-cool-access.md

@@ -28,7 +28,6 @@ The storage with cool access feature provides options for the “coolness period
 * To prevent data retrieval from the cool tier to the hot tier during sequential read operations (for example, antivirus or other file scanning operations), set the cool access retrieval policy to **Default** or **Never**. For more information, see [Enable cool access on a new volume](#enable-cool-access-on-a-new-volume).
 * After the capacity pool is configured with the option to support cool access volumes, the setting can't be disabled at the _capacity pool_ level. You can turn on or turn off the cool access setting at the _volume_ level anytime. Turning off the cool access setting at the volume level stops further tiering of data.  
 * Files moved to the cool tier remains there after you disable cool access on a volume. You must perform an I/O operation on _each_ file to return it to the warm tier. 
-* You can't use [large volumes](large-volumes-requirements-considerations.md) with cool access.
 * For the maximum number of volumes supported for cool access per subscription per region, see [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md#resource-limits).
 * Considerations for using cool access with [cross-region replication](cross-region-replication-requirements-considerations.md) and [cross-zone replication](cross-zone-replication-introduction.md):
     * The cool access setting on the destination volume is updated automatically to match the source volume whenever the setting is changed on the source volume or during authorization. The setting is also updated automatically when a reverse resync of the replication is performed, but only if the destination volume is in a cool access-enabled capacity pool. Changes to the cool access setting on the destination volume don't affect the setting on the source volume.

articles/azure-netapp-files/snapshots-introduction.md

@@ -81,7 +81,7 @@ You can use several methods to create and maintain snapshots:
     * Snapshot policies, via the [Azure portal](snapshots-manage-policy.md), [REST API](/rest/api/netapp/snapshotpolicies), [Azure CLI](/cli/azure/netappfiles/snapshot/policy), or [PowerShell](/powershell/module/az.netappfiles/new-aznetappfilessnapshotpolicy) tools
     * Application consistent snapshot tooling such as [AzAcSnap](azacsnap-introduction.md) or third-party solutions
 
-## How volumes and snapshots are replicated cross-region for disaster recovery and business continuity 
+## How volumes and snapshots are replicated for disaster recovery and business continuity 
 
 Azure NetApp Files supports [cross-region replication](cross-region-replication-introduction.md) for disaster-recovery (DR) purposes and [cross-zone replication](cross-zone-replication-introduction.md) for business continuity. Azure NetApp Files cross-region replication and cross-zone replication both use SnapMirror technology. Only changed blocks are sent over the network in a compressed, efficient format. After replication is initiated between volumes, the entire volume contents (that is, the actual stored data blocks) are transferred only once. This operation is called a *baseline transfer*. After the initial transfer, only changed blocks (as captured in snapshots) are transferred. The result is an asynchronous 1:1 replica of the source volume, including all snapshots. This behavior follows a full and incremental-forever replication mechanism. This technology minimizes the amount of data required for replication, therefore saving data transfer costs. It also shortens the replication time. You can achieve a smaller Recovery Point Objective (RPO), because more snapshots can be created and transferred more frequently with minimal data transfers. Further, it takes away the need for host-based replication mechanisms, avoiding virtual machine and software license cost.
 

articles/azure-vmware/media/nsxt/nsx-create-tier-1.png

@@ -33,13 +33,15 @@ items:
     href: tutorial-configure-networking.md
   - name: 4 - Access a private cloud
     href: tutorial-access-private-cloud.md
-  - name: 5 - Create an NSX network segment
+  - name: 5 - Create an NSX Tier-1 Gateway
+    href: tutorial-nsx-tier-1-gateway.md
+  - name: 6 - Create an NSX network segment
     href: tutorial-nsx-t-network-segment.md
-  - name: 6 - Peer on-premises to private cloud
+  - name: 7 - Peer on-premises to private cloud
     href: tutorial-expressroute-global-reach-private-cloud.md
-  - name: 7 - Scale a private cloud
+  - name: 8 - Scale a private cloud
     href: tutorial-scale-private-cloud.md
-  - name: 8 - Delete a private cloud
+  - name: 9 - Delete a private cloud
     href: tutorial-delete-private-cloud.md
 - name: Cost optimization
   items:

articles/azure-vmware/toc.yml

@@ -0,0 +1,64 @@
+---
+title:  Tutorial - NSX-Tier-1-Gateway
+description: Learn how to create a Tier-1 Gateway
+ms.topic: tutorial
+ms.service: azure-vmware
+ms.date: 12/11/2024
+ms.custom: engagement-fy25
+---
+
+# Tutorial: Create an NSX Tier-1 Gateway 
+
+After deploying the Azure VMware Solution, you can create additional Tier-1 Gateways from the NSX Manager. Once configured, the additional Tier-1 Gateway is visible in the NSX Manager. NSX comes pre-provisioned by default with an NSX Tier-0 Gateway in **Active/Active** mode and a default Tier-1 Gateway in **Active/Standby** mode. 
+
+In this tutorial, you learn how to:
+
+> [!div class="checklist"]
+> * Create an additional NSX Tier-1 Gateway in the NSX Manager
+> * Configure the High Availability (HA) mode on a Tier-1 Gateway 
+
+## Prerequisites
+
+An Azure VMware Solution private cloud with access to the NSX Manager interface. For more information, see the [Configure networking](tutorial-configure-networking.md) tutorial. 
+
+## Use NSX Manager to create a Tier-1 Gateway
+
+A Tier-1 Gateway is typically added to a Tier-0 Gateway in the northbound direction and to segments in the southbound direction. 
+
+1. With the CloudAdmin account, sign-in to the NSX Manager.
+
+2. In NSX Manager, select **Networking** > **Tier-1 Gateways**.
+
+3. Select **Add Tier-1 Gateway**. 
+
+4. Enter a name for the gateway. 
+
+5. Select the **HA Mode** for the Tier-1 Gateway. Choose between **Active/Standby**, **Active/Active**, or **Distributed Only**:
+ 
+    | HA Mode | Description |
+    | :--------- | :------------- |
+    | Active Standby | One active instance and one standby instance. The Standby takes over is the active fails. |
+    | Active Active | Both instances are active and can handle traffic simultaneously. |
+    | Distributed Only | No centralized instances; routing is distributed across all transport nodes. |
+
+6. Select a Tier-0 Gateway to connect to this Tier-1 Gateway to create a multi-tier topology. 
+
+7. Select an NSX Edge cluster if you want this Tier-1 Gateway to host stateful services such as NAT, load balancer, or firewall. 
+
+8. After you select an NSX Edge cluster, a toggle gives you the option to select NSX Edge Nodes. 
+
+9. If you selected an NSX Edge cluster, select a failover mode or accept the default. 
+
+     | Option | Description | 
+     | :----- | :---------- |
+     | Preemptive | If the preferred NSX Edge node fails and recovers, it preempts its peer and becomes the active node. The peer changes its state to standby. |
+     | Non-preemptive  | If the preferred NSX Edge node fails and recovers, it checks if its peer is the active node. If so, the preferred node will not preempt its peer and will be the standby node. This is the default option. |
+
+:::image type="content" source="media/nsxt/nsx-create-tier-1.png" alt-text="Diagram showing the creation of a new Tier-1 Gateway in NSX Manager." border="false" lightbox="media/nsxt/nsx-create-tier-1.png":::
+
+10. Select **Save**. 
+
+## Next steps
+
+In this tutorial, you created an additional Tier-1 Gateway to use in your Azure VMware Solution private cloud. 
+

articles/azure-vmware/tutorial-nsx-tier-1-gateway.md

@@ -4,29 +4,38 @@ description: In this tutorial, use the NYC Taxi sample data to explore SQL pool'
 author: whhender
 ms.author: whhender
 ms.reviewer: whhender, wiassaf
-ms.date: 10/16/2023
+ms.date: 12/11/2024
 ms.service: azure-synapse-analytics
 ms.subservice: sql
 ms.topic: tutorial
 ms.custom: engagement-fy23
 ---
 
-# Analyze data with dedicated SQL pools
+# Tutorial: Analyze data with dedicated SQL pools
 
 In this tutorial, use the NYC Taxi data to explore a dedicated SQL pool's capabilities.
 
+> [!div class="checklist"]
+> * [Deploy a dedicated SQL pool]
+> * [Load data into the pool]
+> * [Explore the data you've loaded]
+
+## Prerequisites
+
+* This tutorial assumes you've completed the steps in the rest of the quickstarts. Specifically it uses the 'contosodatalake' resource created in [the Create a Synapse Workspace quickstart.](get-started-create-workspace.md#place-sample-data-into-the-primary-storage-account)
+
 ## Create a dedicated SQL pool
 
 1. In Synapse Studio, on the left-side pane, select **Manage** > **SQL pools** under **Analytics pools**.
 1. Select **New**.
 1. For **Dedicated SQL pool name** select `SQLPOOL1`.
 1. For **Performance level** choose **DW100C**.
-1. Select **Review + create** > **Create**. Your dedicated SQL pool will be ready in a few minutes. 
+1. Select **Review + create** > **Create**. Your dedicated SQL pool will be ready in a few minutes.
 
 Your dedicated SQL pool is associated with a SQL database that's also called `SQLPOOL1`.
 
 1. Navigate to **Data** > **Workspace**.
-1. You should see a database named **SQLPOOL1**. If you do not see it, select **Refresh**.
+1. You should see a database named **SQLPOOL1**. If you don't see it, select **Refresh**.
 
 A dedicated SQL pool consumes billable resources as long as it's active. You can pause the pool later to reduce costs.
 
@@ -83,13 +92,20 @@ A dedicated SQL pool consumes billable resources as long as it's active. You can
         ,IDENTITY_INSERT = 'OFF'
     )
     ```
+
+    >[!TIP]
+    >If you get an error that reads `Login failed for user '<token-identified principal>'`, you need to set your Entra Id admin. 
+    > 1. In the Azure Portal, search for your synapse workspace.
+    > 1. Under **Settings** select **Microsoft Entra ID**.
+    > 1. Select **Set admin** and set a Microsoft Entra ID admin.
+
 1. Select the **Run** button to execute the script.
 1. This script finishes in less than 60 seconds. It loads 2 million rows of NYC Taxi data into a table called `dbo.NYCTaxiTripSmall`.
 
 ## Explore the NYC Taxi data in the dedicated SQL pool
 
 1. In Synapse Studio, go to the **Data** hub.
-1. Go to **SQLPOOL1** > **Tables**. 
+1. Go to **SQLPOOL1** > **Tables**. (If you don't see it in the menu, refresh the page.)
 1. Right-click the **dbo.NYCTaxiTripSmall** table and select **New SQL Script** > **Select TOP 100 Rows**.
 1. Wait while a new SQL script is created and runs.
 1. At the top of the SQL script **Connect to** is automatically set to the SQL pool called **SQLPOOL1**.
@@ -110,7 +126,16 @@ A dedicated SQL pool consumes billable resources as long as it's active. You can
 
     This query creates a table `dbo.PassengerCountStats` with aggregate data from the `trip_distance` field, then queries the new table. The data shows how the total trip distances and average trip distance relate to the number of passengers.
 1. In the SQL script result window, change the **View** to **Chart** to see a visualization of the results as a line chart. Change **Category column** to `PassengerCount`.
-    
+
+## Clean up
+
+Pause your dedicated SQL Pool to reduce costs.
+
+1. Navigate to **Manage** in your synapse workspace.
+1. Select **SQL pools**.
+1. Hover over SQLPOOL1 and select the **Pause** button.
+1. Confirm to pause.
+
 ## Next step
 
 > [!div class="nextstepaction"]

articles/synapse-analytics/get-started-analyze-sql-pool.md

@@ -1,14 +1,14 @@
 ---
 title: Apache Spark pool concepts
 description: Introduction to Apache Spark pool sizes and configurations in Azure Synapse Analytics.
-ms.topic: conceptual
+ms.topic: concept-article
 ms.service: azure-synapse-analytics
 ms.subservice: spark
 ms.custom: references_regions
 author: guyhay
 ms.author: guyhay
 ms.reviewer: whhender
-ms.date: 09/07/2022 
+ms.date: 12/06/2024
 ---
 
 # Apache Spark pool configurations in Azure Synapse Analytics
@@ -53,7 +53,7 @@ Autoscale for Apache Spark pools allows automatic scale up and down of compute r
 Apache Spark pools now support elastic pool storage. Elastic pool storage allows the Spark engine to monitor worker node temporary storage and attach extra disks if needed. Apache Spark pools utilize temporary disk storage while the pool is instantiated. Spark jobs write shuffle map outputs, shuffle data and spilled data to local VM disks. Examples of operations that could utilize local disk are sort, cache, and persist. When temporary VM disk space runs out, Spark jobs could fail due to “Out of Disk Space” error (java.io.IOException: No space left on device). With “Out of Disk Space” errors, much of the burden to prevent jobs from failing shifts to the customer to reconfigure the Spark jobs (for example, tweak the number of partitions) or clusters (for example, add more nodes to the cluster). These errors might not be consistent, and the user might end up experimenting heavily by running production jobs. This process can be expensive for the user in multiple dimensions:
 
 * Wasted time. Customers are required to experiment heavily with job configurations via trial and error and are expected to understand Spark’s internal metrics to make the correct decision.
-* Wasted resources. Since production jobs can process varying amount of data, Spark jobs can fail non-deterministically if resources aren't over-provisioned. For instance, consider the problem of data skew, which could result in a few nodes requiring more disk space than others. Currently in Synapse, each node in a cluster gets the same size of disk space and increasing disk space across all nodes isn't an ideal solution and leads to tremendous waste.
+* Wasted resources. Since production jobs can process varying amount of data, Spark jobs can fail nondeterministically if resources aren't over-provisioned. For instance, consider the problem of data skew, which could result in a few nodes requiring more disk space than others. Currently in Synapse, each node in a cluster gets the same size of disk space and increasing disk space across all nodes isn't an ideal solution and leads to tremendous waste.
 * Slowdown in job execution. In the hypothetical scenario where we solve the problem by autoscaling nodes (assuming costs aren't an issue to the end customer), adding a compute node is still expensive (takes a few minutes) as opposed to adding storage (takes a few seconds).
 
 No action is required by you, plus you should see fewer job failures as a result.
@@ -65,7 +65,7 @@ No action is required by you, plus you should see fewer job failures as a result
 
 The automatic pause feature releases resources after a set idle period, reducing the overall cost of an Apache Spark pool. The number of minutes of idle time can be set once this feature is enabled. The automatic pause feature is independent of the autoscale feature. Resources can be paused whether the autoscale is enabled or disabled. This setting can be altered after pool creation although active sessions will need to be restarted.
 
-## Next steps
+## Related content
 
 * [Azure Synapse Analytics](../index.yml)
 * [Apache Spark Documentation](https://spark.apache.org/docs/3.2.1/)