Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-custom-roles-rest-api

Author: rolyon

articles/aks/TOC.yml

@@ -221,6 +221,8 @@
           href: free-standard-pricing-tiers.md
         - name: Use Draft (preview)
           href: draft.md
+        - name: Use Draft and the DevX extension for Visual Studio Code (preview)
+          href: draft-devx-extension-aks.md
         - name: Use proximity placement groups
           href: reduce-latency-ppg.md
         - name: Upgrade the node image

articles/aks/draft-devx-extension-aks.md

@@ -0,0 +1,77 @@
+---
+title: Use Draft and the DevX extension for Visual Studio Code with Azure Kubernetes Service (AKS) (preview)
+description: Learn how to use Draft and the DevX extension for Visual Studio Code with Azure Kubernetes Service (AKS)
+author: schaffererin
+ms.topic: article
+ms.date: 03/20/2023
+ms.author: schaffererin
+---
+
+# Use Draft and the DevX extension for Visual Studio Code with Azure Kubernetes Service (AKS) (preview)
+
+[Draft][draft] is an open-source project that streamlines Kubernetes development by taking a non-containerized application and generating the DockerFiles, Kubernetes manifests, Helm charts, Kustomize configurations, and other artifacts associated with a containerized application. The Azure Kubernetes Service (AKS) DevX extension for Visual Studio Code enhances non-cluster experiences, allowing you to create deployment files to deploy your applications to AKS. Draft is the available feature included in the DevX extension.
+
+This article shows you how to use Draft with the DevX extension to draft a DockerFile, draft a Kubernetes deployment and service, and build an image on Azure Container Registry (ACR).
+
+[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
+
+## Before you begin
+
+* You need an Azure resource group and an AKS cluster with an attached ACR. To attach an ACR to your AKS cluster, use `az aks update -n <cluster-name> -g <resource-group-name> --attach-acr <acr-name>` or follow the instructions in [Authenticate with ACR from AKS][aks-acr-authenticate].
+* Download and install the [Azure Kubernetes Service DevX Extension for Visual Studio Code][devx-extension].
+
+## Draft with the DevX extension for Visual Studio Code
+
+To get started with Draft in Visual Studio Code, press **Ctrl + Shift + P** in your Visual Studio Code window and enter **AKS Developer**. From here, you'll see available Draft commands:
+
+* Get started
+* Draft a DockerFile
+* Draft a Kubernetes Deployment and Service
+* Build an Image on Azure Container Registry
+
+### Get started
+
+The `Get started` command shows you all the steps you need to get up and running on AKS.
+
+1. Press **Ctrl + Shift + P** to open the command palette.
+2. Enter **AKS Developer**.
+3. Select **AKS Developer: Get started**.
+
+You'll see the following getting started page:
+
+:::image type="content" source="./media/draft-devx-extension-aks/draft-devx-extension-aks-get-started-page-vs-code.png" alt-text="Screenshot showing the Get started page in Visual Studio Code." lightbox="./media/draft-devx-extension-aks/draft-devx-extension-aks-get-started-page-vs-code.png":::
+
+### Draft a DockerFile
+
+`Draft a DockerFile` adds the minimum required DockerFile to your project directory.
+
+1. Press **Ctrl + Shift + P** to open the command palette.
+2. Enter **AKS Developer**.
+3. Select **AKS Developer: Draft a DockerFile**.
+
+### Draft a Kubernetes Deployment and Service
+
+`Draft a Kubernetes Deployment and Service` adds the appropriate deployment and service files to your application, which allows you to deploy to your AKS cluster. The supported deployment types include: Helm, Kustomize, and Kubernetes manifests.
+
+1. Press **Ctrl + Shift + P** to open the command palette.
+2. Enter **AKS Developer**.
+3. Select **AKS Developer: Draft a Kubernetes Deployment and Service**.
+
+### Build an Image on Azure Container Registry
+
+`Build an Image on Azure Container Registry` builds an image on your ACR to use in your deployment files.
+
+1. Press **Ctrl + Shift + P** to open the command palette.
+2. Enter **AKS Developer**.
+3. Select **AKS Developer: Build an Image on Azure Container Registry**.
+
+## Next steps
+
+In this article, you learned how to use Draft and the DevX extension for Visual Studio Code with AKS. To use Draft with the Azure CLI, see [Draft for AKS][draft-aks-cli].
+
+<!-- LINKS -->
+
+[draft-aks-cli]: ../aks/draft.md
+[aks-acr-authenticate]: ../aks/cluster-container-registry-integration.md
+[devx-extension]: https://marketplace.visualstudio.com/items?itemName=ms-kubernetes-tools.aks-devx-tools
+[draft]: https://github.com/Azure/draft

articles/aks/media/draft-devx-extension-aks/draft-devx-extension-aks-get-started-page-vs-code.png

@@ -11,7 +11,7 @@ ms.custom: include file
 ms.author: dbasantes
 ---
 
-### Using Azure blob storage for external storage
+## Using Azure blob storage for external storage
 
 ```csharp
 StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCallLocator("<serverCallId>"))

articles/communication-services/quickstarts/call-automation/includes/recording-byos-private-csharp.md

@@ -9,7 +9,7 @@ ms.author: kendownie
 ms.subservice: files
 ---
 
-# Deprovision your Azure File Sync server endpoint
+# Deprovision or delete your Azure File Sync server endpoint
 
 Removing a server endpoint means stopping sync to and from that server location with the cloud endpoint (Azure file share) in the same sync group. Before you deprovision your server endpoint, there are a few steps you should take to maintain data integrity and availability. This article covers several methods of deprovisioning and the appropriate guidance, ordered by scenario. Follow the steps for the use case that best applies to you.
 

articles/storage/file-sync/file-sync-server-endpoint-delete.md

@@ -58,20 +58,10 @@ Select the **Add to pipeline** button on the upper right corner to add a noteboo
 
 ### Designate a parameters cell
 
-# [Classic notebook](#tab/classical)
-
-To parameterize your notebook, select the ellipses (...) to access the other cell actions menu at the far right. Then select **Toggle parameter cell** to designate the cell as the parameters cell.
-
-[![screenshot-showing-toggle-parameter](./media/synapse-notebook-activity/toggle-parameter-cell.png)](./media/synapse-notebook-activity/toggle-parameter-cell.png#lightbox)
-
-# [Preview notebook](#tab/preview)
-
 To parameterize your notebook, select the ellipses (...) to access the **more commands** at the cell toolbar. Then select **Toggle parameter cell** to designate the cell as the parameters cell.
 
 [![screenshot-showing-azure-notebook-toggle-parameter](./media/synapse-notebook-activity/azure-notebook-toggle-parameter-cell.png)](./media/synapse-notebook-activity/azure-notebook-toggle-parameter-cell.png#lightbox)
 
----
-
 Azure Data Factory looks for the parameters cell and uses the values as defaults for the parameters passed in at execution time. The execution engine will add a new cell beneath the parameters cell with input parameters to overwrite the default values. 
 
 
@@ -108,10 +98,6 @@ You can reference other notebooks in a Synapse notebook activity via calling [%r
 - [%run magic](./spark/apache-spark-development-using-notebooks.md#notebook-reference) copies all cells from the referenced notebook to the %run cell and shares the variable context. When notebook1 references notebook2 via `%run notebook2` and notebook2 calls a [mssparkutils.notebook.exit](./spark/microsoft-spark-utilities.md#exit-a-notebook) function, the cell execution in notebook1 will be stopped. We recommend you use %run magic when you want to "include" a notebook file.
 - [mssparkutils notebook utilities](./spark/microsoft-spark-utilities.md#notebook-utilities) calls the referenced notebook as a method or a function. The variable context isn't shared. When notebook1 references notebook2 via `mssparkutils.notebook.run("notebook2")` and notebook2 calls a [mssparkutils.notebook.exit](./spark/microsoft-spark-utilities.md#exit-a-notebook) function, the cell execution in notebook1 will continue. We recommend you use mssparkutils notebook utilities when you want to  "import" a notebook.
 
->[!Note]
-> Run another Synapse notebook from a Synapse pipeline will only work for a notebook with Preview enabled.
-
-
 ## See notebook activity run history
 
 Go to **Pipeline runs** under the **Monitor** tab, you'll see the pipeline you have triggered. Open the pipeline that contains notebook activity to see the run history. 
@@ -215,4 +201,4 @@ Here's the sample JSON of a Synapse notebook activity output:
 
 ```
 ## Known issues
-If the notebook name is parametrized in the Pipeline Notebook activity, then the notebook version in unpublished status can't be referenced in the debug runs.
+If the notebook name is parametrized in the Pipeline Notebook activity, then the notebook version in unpublished status can't be referenced in the debug runs.