Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-elevate-access-manage-users

Author: rolyon

articles/azure-resource-manager/bicep/deploy-vscode.md

@@ -3,14 +3,14 @@ title: Deploy Bicep files with Visual Studio Code
 description: Deploy Bicep files from Visual Studio Code.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 12/03/2024
 ---
 
 # Deploy Bicep files from Visual Studio Code
 
 You can use [Visual Studio Code with the Bicep extension](./visual-studio-code.md#deploy-bicep-file) to deploy a Bicep file. You can deploy to any scope. This article shows deploying to a resource group.
 
-From an opened Bicep file in VS Code, there are there ways you can find the command:
+From an opened Bicep file in VS Code, there are three ways you can find the command:
 
 - Right-click the Bicep file name from the Explorer pane, not the one under **OPEN EDITORS**:
 
@@ -24,9 +24,9 @@ From an opened Bicep file in VS Code, there are there ways you can find the comm
 
 After you select the command, you follow the wizard to enter the values:
 
-1. Sign in to Azure and select subscription.
+1. If you're not signed in, follow the instructions provided in the prompt to complete the sign-in process.
 
-    :::image type="content" source="./media/deploy-vscode/bicep-deploy-select-subscription.png" alt-text="Screenshot of Select subscription.":::
+    :::image type="content" source="./media/deploy-vscode/bicep-deploy-sign-in.png" alt-text="Screenshot of sign-in.":::
 
     [!INCLUDE [vscode authentication](../../../includes/resource-manager-vscode-authentication.md)]
 

articles/azure-resource-manager/bicep/media/deploy-vscode/bicep-deploy-select-subscription.png

@@ -19,7 +19,7 @@
 - name: Quickstarts
   items:
   - name: Create Bicep templates - VS Code
-    displayName: vscode
+    displayName: vscode,vs code
     href: quickstart-create-bicep-use-visual-studio-code.md
   - name: Create Bicep templates - Visual Studio
     href: quickstart-create-bicep-use-visual-studio.md

articles/azure-resource-manager/bicep/media/deploy-vscode/bicep-deploy-sign-in.png

@@ -3,7 +3,7 @@ title: Create Bicep files by using Visual Studio Code
 description: Learn how to use Visual Studio Code to create Bicep files.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 10/14/2024
+ms.date: 11/20/2024
 ---
 
 # Create Bicep files by using Visual Studio Code

articles/azure-resource-manager/bicep/media/visual-studio-code/visual-studio-code-bicep-view-type-document.png

@@ -42,7 +42,7 @@ For copy running on Self-hosted IR with Parquet file serialization/deserializati
 
 - **To use JRE**: The 64-bit IR requires 64-bit JRE. You can find it from [here](https://go.microsoft.com/fwlink/?LinkId=808605).
 - **To use JDK**: The 64-but IR requires 64-bit JDK 23. You can find it from [here](https://www.oracle.com/java/technologies/downloads/#jdk23-windows). Be sure to update the `JAVA_HOME` system variable to the root folder of the JDK 23 installation i.e. `C:\Program Files\Java\jdk-23`, and add the path to both the `C:\Program Files\Java\jdk-23\bin` and `C:\Program Files\Java\jdk-23\bin\server` folders to the `Path` system variable.
-- **To use OpenJDK**: It's supported since IR version 3.13. Package the jvm.dll with all other required assemblies of OpenJDK into Self-hosted IR machine, and set system environment variable JAVA_HOME accordingly, and then restart Self-hosted IR for taking effect immediately.
+- **To use OpenJDK**: It's supported since IR version 3.13. Package the jvm.dll with all other required assemblies of OpenJDK into Self-hosted IR machine, and set system environment variable JAVA_HOME accordingly, and then restart Self-hosted IR for taking effect immediately. To download the Microsoft Build of OpenJDK, see [Microsoft Build of OpenJDK™](https://www.microsoft.com/openjdk).
 
 > [!TIP]
 > If you copy data to/from Parquet format using Self-hosted Integration Runtime and hit error saying "An error occurred when invoking java, message: **java.lang.OutOfMemoryError:Java heap space**", you can add an environment variable `_JAVA_OPTIONS` in the machine that hosts the Self-hosted IR to adjust the min/max heap size for JVM to empower such copy, then rerun the pipeline.

articles/azure-resource-manager/bicep/toc.yml

@@ -5,9 +5,9 @@ services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: how-to
-ms.date: 09/11/2023
+ms.date: 12/03/2024
 ms.author: duau
-ms.custom: devx-track-azurepowershell, template-tutorial
+ms.custom: devx-track-azurepowershell
 ---
 # Configure a virtual network gateway for ExpressRoute using PowerShell
 > [!div class="op_single_selector"]
@@ -16,15 +16,15 @@ ms.custom: devx-track-azurepowershell, template-tutorial
 > * [Classic - PowerShell](expressroute-howto-add-gateway-classic.md)
 > 
 
-This article walks you through the steps to add, resize, and remove a virtual network gateway for a pre-existing virtual network (VNet) using PowerShell. The steps for this configuration apply to VNets that were created using the Resource Manager deployment model for an ExpressRoute configuration. For more information about virtual network gateways and gateway configuration settings for ExpressRoute, see [About virtual network gateways for ExpressRoute](expressroute-about-virtual-network-gateways.md).
+This article walks you through the steps to add, resize, and remove a virtual network gateway for a preexisting virtual network (VNet) using PowerShell. The steps for this configuration apply to VNets that were created using the Resource Manager deployment model for an ExpressRoute configuration. For more information about virtual network gateways and gateway configuration settings for ExpressRoute, see [About virtual network gateways for ExpressRoute](expressroute-about-virtual-network-gateways.md).
 
 :::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/gateway-circuit.png" alt-text="Diagram showing an ExpressRoute gateway connected to the ExpressRoute circuit." lightbox="./media/expressroute-howto-add-gateway-portal-resource-manager/gateway-circuit.png":::
 
 ## Prerequisites
 
 ### Configuration reference list
 
-The steps for this task use a VNet based on the values in the following configuration reference list. Additional settings and names are also outlined in this list. We don't use this list directly in any of the steps, although we do add variables based on the values in this list. You can copy the list to use as a reference, replacing the values with your own.
+The steps for this task use a VNet based on the values in the following configuration reference list. More settings and names are also outlined in this list. We don't use this list directly in any of the steps, although we do add variables based on the values in this list. You can copy the list to use as a reference, replacing the values with your own.
 
 | Setting                   | Value                                              |
 | ---                       | ---                                                |
@@ -36,7 +36,7 @@ The steps for this task use a VNet based on the values in the following configur
 | Subnet1 Name | *FrontEnd* |
 | Gateway Subnet name | *GatewaySubnet* |    
 | Gateway Subnet address space | *192.168.200.0/26* |
-| Region | *East US* |
+| Region | *West US* |
 | Gateway Name | *GW* |   
 | Gateway IP Name | *GWIP* |
 | Gateway IP configuration Name | *gwipconf* |
@@ -55,7 +55,19 @@ The steps for this task use a VNet based on the values in the following configur
 
    ```azurepowershell-interactive 
    $RG = "TestRG"
-   $Location = "East US"
+   $Location = "West US"
+   $GWName = "GW"
+   $GWIPName = "GWIP"
+   $GWIPconfName = "gwipconf"
+   $VNetName = "TestVNet"
+   ```
+
+    If you want to create the gateway in an Azure Extended Zone, add the **$ExtendedLocation** variable.
+
+   ```azurepowershell-interactive 
+   $RG = "TestRG"
+   $Location = "West US"
+   $ExtendedLocation = "losangeles"
    $GWName = "GW"
    $GWIPName = "GWIP"
    $GWIPconfName = "gwipconf"
@@ -90,6 +102,11 @@ The steps for this task use a VNet based on the values in the following configur
 
    ```azurepowershell-interactive
    $pip = New-AzPublicIpAddress -Name $GWIPName  -ResourceGroupName $RG -Location $Location -AllocationMethod Static -SKU Standard
+   ```
+    If you want to create the gateway in an Azure Extended Zone, request a public IP address in the Extended Zone using the **-ExtendedLocation** parameter.
+
+   ```azurepowershell-interactive
+   $pip = New-AzPublicIpAddress -Name $GWIPName  -ResourceGroupName $RG -Location $Location -ExtendedLocation $ExtendedLocation -AllocationMethod Static -SKU Standard
    ```
 
    > [!NOTE]
@@ -105,6 +122,11 @@ The steps for this task use a VNet based on the values in the following configur
    ```azurepowershell-interactive
    New-AzVirtualNetworkGateway -Name $GWName -ResourceGroupName $RG -Location $Location -IpConfigurations $ipconf -GatewayType Expressroute -GatewaySku Standard
    ```
+    If you want to create the gateway in an Azure Extended Zone, add the **-ExtendedLocation** parameter.
+
+   ```azurepowershell-interactive
+   New-AzVirtualNetworkGateway -Name $GWName -ResourceGroupName $RG -Location $Location -ExtendedLocation $ExtendedLocation -IpConfigurations $ipconf -GatewayType Expressroute -GatewaySku Standard
+   ```
 
 ## Verify the gateway was created
 

articles/azure-resource-manager/bicep/visual-studio-code.md

@@ -40,6 +40,7 @@ After submitting the request, you'll see its status. To verify the successful cr
 You can also see that the *Approval State* is *Pending*. The owner of the target resource can approve or deny the private endpoint connection request. If the owner approves the private endpoint connection request, then a private link is established. If denied, then a private link isn't established.
 ![Managed private endpoint creation request status](./media/how-to-create-managed-private-endpoints/managed-private-endpoint-5.png)
 
-## Next steps
+## Related content
 
-Learn more about [Managed private endpoints](./synapse-workspace-managed-private-endpoints.md)
+- You can also [deploy managed private endpoints using the Azure CLI](/cli/azure/synapse/managed-private-endpoints).
+- Learn more about [managed private endpoints](./synapse-workspace-managed-private-endpoints.md).

articles/data-factory/format-parquet.md

@@ -4,7 +4,7 @@ description: Learn how to add and manage libraries to workspace in Azure Synapse
 author: shuaijunye
 ms.service: azure-synapse-analytics
 ms.topic: conceptual
-ms.date: 11/03/2022
+ms.date: 12/03/2024
 ms.author: shuaijunye
 ms.subservice: spark
 ---
@@ -15,8 +15,8 @@ Workspace packages can be custom or private wheel (Python), jar (Scala/Java), or
 
 To add workspace packages:
 1. Navigate to the **Manage** > **Workspace packages** tab.
-2. Upload your wheel files by using the file selector.
-3. Once the files have been uploaded to the Azure Synapse workspace, you can add these packages to a given Apache Spark pool.
+2. Upload your files using the file selector.
+3. Once the files have been uploaded to the Azure Synapse workspace, you can add these packages to an Apache Spark pool.
 
   :::image type="content" source="./media/apache-spark-azure-portal-add-libraries/studio-add-workspace-package.png" alt-text="Screenshot that highlights workspace packages." lightbox="./media/apache-spark-azure-portal-add-libraries/studio-add-workspace-package.png":::
 
@@ -26,10 +26,10 @@ To add workspace packages:
 >- Once Workspace Packages are used to install packages on a given Apache Spark pool, there is a limitation that you can no longer specify packages using the Storage account path on the same pool.  
 
 > [!NOTE]
-> It's recommended that you don't have multiple wheel packages with the same name in a workspace. If you want to use a different version of the same wheel package, you have to delete the existing version and upload the new one.
+> It's recommended that you don't have multiple packages with the same name in a workspace. If you want to use a different version of the same package, you have to delete the existing version and upload the new one.
 
 ## Storage account
-Custom-built wheel packages can be installed on the Apache Spark pool by uploading all the wheel files into the Azure Data Lake Storage (Gen2) account that is linked with the Synapse workspace. 
+Custom-built packages can be installed on the Apache Spark pool by uploading all the files into the Azure Data Lake Storage (Gen2) account that is linked with the Synapse workspace. 
 
 The files should be uploaded to the following path in the storage account's default container: 
 
@@ -39,7 +39,7 @@ abfss://<file_system>@<account_name>.dfs.core.windows.net/synapse/workspaces/<wo
 
 >[!WARNING]
 > - In some cases, you may need to create the file path based on the structure above if it does not already exist. For example, you may need to add the ```python``` folder within the ```libraries``` folder if it does not already exist.
-> - This method of managing custom wheel files will not be supported on the Azure Synapse Runtime for Apache Spark 3.0. Please refer to the Workspace packages feature to manage custom wheel files.
+> - This method of managing custom files will not be supported on the Azure Synapse Runtime for Apache Spark 3.0. Please refer to the Workspace packages feature to manage custom files.
 
 > [!IMPORTANT]
 > To install custom libraries using the Azure DataLake Storage method, you must have the **Storage Blob Data Contributor** or **Storage Blob Data Owner** permissions on the primary Gen2 Storage account that is linked to the Azure Synapse Analytics workspace.