Merge pull request #287708 from MicrosoftDocs/main

10/01/2024 PM Publish

Author: Daidihuang

articles/azure-netapp-files/cross-region-replication-introduction.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 09/10/2024
+ms.date: 10/01/2024
 ms.author: anfdocs
 ms.custom: references_regions
 ---
@@ -53,6 +53,7 @@ Azure NetApp Files volume replication is supported between various [Azure region
 | Germany/Europe | Germany West Central | West Europe | 
 | Germany/France | Germany West Central | France Central |
 | Spain/Sweden | Spain Central | Sweden Central |
+| Sweden/Germany | Sweden Central | Germany West Central |
 | Qatar/Europe | Qatar Central | West Europe |
 | North America | East US | East US 2 |
 | North America | East US 2| West US 2 |

articles/azure-vmware/media/self-service-orchestration/operations-maintenance.png

@@ -0,0 +1,55 @@
+---
+title: Self service maintenance orchestration (public preview)
+description: Learn how to enable self service maintenance orchestration.
+author: jjaygbay1
+ms.author: jacobjaygbay
+ms.topic: conceptual
+ms.service: azure-vmware
+ms.date: 06/25/2024
+ms.custom: engagement-fy24
+---
+
+# Self service maintenance orchestration (public preview)
+
+In this article, you learn about one of the advantages of Azure VMware Solution private cloud. The advantage is the managed platform where Microsoft handles the lifecycle management of VMware software (ESXi, vCenter Server, and vSAN) and NSX appliances. Microsoft also takes care of applying any patches, updates, or upgrades to ESXi, vCenter Server, vSAN, and NSX within your private cloud. 
+Regular upgrades of the Azure VMware Solution private cloud and VMware software ensure the latest security, stability, and feature sets are running in your private cloud. For more information, see [Host maintenance and lifecycle management](architecture-private-clouds.md).
+
+Microsoft schedules maintenance and notifies customers through Service Health notifications. The details of the planned maintenance are available under the planned maintenance section. Currently, customers must raise a support ticket if they wish to change a scheduled maintenance window.
+The Self-Service Maintenance orchestration feature provides customers with the flexibility to reschedule their planned maintenance directly from the Azure portal.
+
+## Prerequisites
+
+- An existing Azure VMware Solution private cloud.
+- A registered subscription to the Microsoft Azure VMware Solution AFEC flags named Early Access and Self Serve for Maintenance. You can find these flags under **Preview Features** on the Azure portal.
+ 
+## Reschedule maintenance through Azure VMware Solution maintenance
+
+1. Sign in to your Azure VMware Solution private cloud.
+ 
+    >[!Note]
+    > At least a contributor level access on the Azure VMware Solution private cloud is required.
+
+1. From the left navigation, locate **Operations** and select **Maintenance** from the drop-down list.
+
+    :::image type="content" source="media/self-service-orchestration/operations-maintenance.png" alt-text="Screenshot that shows how to set up self-service maintenance." lightbox="media/self-service-orchestration/operations-maintenance.png":::
+    
+1. Under the **Upcoming maintenance** tab, select the **Reschedule** option located on the right side.
+
+     :::image type="content" source="media/self-service-orchestration/reschedule-maintenance.png" alt-text="Screenshot that shows how to reschedule maintenance." lightbox="media/self-service-orchestration/reschedule-maintenance.png":::
+
+      
+ 
+1. Input the revised date and time, then select **Reschedule**. 
+    
+      :::image type="content" source="media/self-service-orchestration/upcoming-maintenance.png" alt-text="Screenshot that shows how to review upcoming maintenance schedule." lightbox="media/self-service-orchestration/upcoming-maintenance.png":::
+ 
+ After you’ve selected **Reschedule**, the system modifies the schedule to the new date and the new schedule is displayed to the portal.
+
+## Additional Information
+The following system error or warning messages appear while trying to reschedule maintenance tasks:
+
+ - Users aren't allowed to reschedule maintenance after the upgrade deadline and on freeze days.
+ - Users will be allowed to reschedule up to 1 hour before and after the start of the maintenance. 
+ - Each maintenance task is assigned an internal deadline. Dates that exceed this deadline appear greyed out on the portal. If a customer needs to reschedule maintenance beyond this point, they should raise a support ticket.
+ - Maintenance that is critical or carries fix for a critical security vulnerability, might have the reschedule option greyed out.
+ - This feature is only enabled for a selected set of maintenance, therefore not all the Azure VMware Solution maintenance shows up in this navigation or have the reschedule option.

articles/azure-vmware/media/self-service-orchestration/reschedule-maintenance.png

@@ -311,6 +311,8 @@ items:
     href: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/vmware_private_cloud
   - name: Configure VMware Cloud Director Service in Azure VMware Solution
     href: configure-vmware-cloud-director-service-azure-vmware-solution.md
+  - name: Self service maintenance orchestration (public preview)
+    href: self-service-maintenance-orchestration.md
   - name: Enable VMware Cloud Director Service with Azure VMware solution
     href: enable-vmware-cds-with-azure.md
   - name: Deploy VMware Cloud Director Availability in Azure VMware Solution

articles/azure-vmware/media/self-service-orchestration/upcoming-maintenance.png

@@ -684,7 +684,75 @@ For more information about the properties, see [Lookup activity](control-flow-lo
 
 ## Upgrade the Snowflake linked service
 
-To upgrade the Snowflake linked service, create a new Snowflake linked service and configure it by referring to [Linked service properties](#linked-service-properties). 
+To upgrade the Snowflake linked service, you can do a side-by-side upgrade, or an in-place upgrade.
+
+### Side-by-side upgrade
+
+To perform a side-by-side upgrade, complete the following steps:
+
+1. Create a new Snowflake linked service and configure it by referring to the linked service properties.  
+1. Create a dataset based on the newly created Snowflake linked service.
+1. Replace the new linked service and dataset with the existing ones in the pipelines that targets the legacy objects. 
+
+### In-place upgrade
+
+To perform an in-place upgrade, you need to edit the existing linked service payload.
+
+1. Update the type from ‘Snowflake’ to ‘SnowflakeV2’.
+2. Modify the linked service payload from its legacy format to the new pattern. You can either fill in each field from the user interface after changing the type mentioned above, or update the payload directly through the JSON Editor. Refer to the [Linked service properties](#linked-service-properties) section in this article for the supported connection properties.  The following examples show the differences in payload for the legacy and new Snowflake connectors:
+
+  **Legacy Snowflake connector JSON payload:**
+  ```json
+  { 
+      "name": "Snowflake1", 
+      "type": "Microsoft.DataFactory/factories/linkedservices", 
+      "properties": { 
+          "annotations": [], 
+          "type": "Snowflake", 
+          "typeProperties": { 
+              "authenticationType": "Basic", 
+              "connectionString": "jdbc:snowflake://<fake_account>.snowflakecomputing.com/?user=FAKE_USER&db=FAKE_DB&warehouse=FAKE_DW&schema=PUBLIC", 
+              "encryptedCredential": "<placeholder>" 
+          }, 
+          "connectVia": { 
+              "referenceName": "AzureIntegrationRuntime", 
+              "type": "IntegrationRuntimeReference" 
+          } 
+      }
+  } 
+  ```
+
+  **New Snowflake connector JSON payload:**
+  ```json
+  { 
+      "name": "Snowflake2", 
+      "type": "Microsoft.DataFactory/factories/linkedservices", 
+      "properties": { 
+          "parameters": { 
+             "schema": { 
+                  "type": "string", 
+                  "defaultValue": "PUBLIC" 
+              } 
+          }, 
+          "annotations": [], 
+          "type": "SnowflakeV2", 
+          "typeProperties": { 
+              "authenticationType": "Basic", 
+              "accountIdentifier": "<FAKE_Account", 
+              "user": "FAKE_USER", 
+              "database": "FAKE_DB", 
+              "warehouse": "FAKE_DW", 
+              "encryptedCredential": "<placeholder>" 
+          }, 
+          "connectVia": { 
+              "referenceName": "AutoResolveIntegrationRuntime", 
+              "type": "IntegrationRuntimeReference" 
+          } 
+      } 
+  } 
+  ```
+
+1. Update dataset to use the new linked service. You can either create a new dataset based on the newly created linked service, or update an existing dataset's type property from _SnowflakeTable_ to _SnowflakeV2Table_. 
 
 ## Differences between Snowflake and Snowflake (legacy)
 

articles/azure-vmware/self-service-maintenance-orchestration.md

@@ -115,7 +115,7 @@ You'll need to complete the following steps to enable the trusted Microsoft serv
 
 Similarly, you can use private access endpoints for your Azure Digital Twins instance to allow clients located in your virtual network to have secure REST API access to the instance over Private Link. Configuring a private access endpoint for your Azure Digital Twins instance enables you to secure your Azure Digital Twins instance and eliminate public exposure. Additionally, it helps avoid data exfiltration from your [Azure Virtual Network (VNet)](../virtual-network/virtual-networks-overview.md).
 
-The private access endpoint uses an IP address from your Azure VNet address space. Network traffic between a client on your private network and the Azure Digital Twins instance traverses over the VNet and a Private Link on the Microsoft backbone network, eliminating exposure to the public internet. Here's a visual representation of this system:
+The private access endpoint uses an IP address from your Azure VNet address space. Network traffic between a client on your private network and the Azure Digital Twins instance traverses over the VNet and a Private Link on the Microsoft backbone network, eliminating exposure to the public internet.
 
 :::image type="content" source="media/concepts-security/private-link.png" alt-text="Diagram showing a network that is a protected VNET with no public cloud access, connecting through Private Link to an Azure Digital Twins instance.":::
 

articles/azure-vmware/toc.yml

@@ -58,7 +58,7 @@ This article helps you create a connection to link a virtual network (virtual ne
 
 4. Select the **Connection type** as **ExpressRoute** and then select **Next: Settings >**.
 
-    :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/create-connection-basic-new.png" alt-text="Screenshot of create a connection basic page.":::
+    :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/create-connection-basic.png" alt-text="Screenshot of create a connection basic page.":::
 
 5. Select the resiliency type for your connection. You can choose **Maximum resiliency** or **Standard resiliency**.