Manual fine-tuning

baanders · baanders · commit 99c3207f0906 · 2025-03-04T11:05:05.000-08:00
diff --git a/articles/digital-twins/how-to-authenticate-client.md b/articles/digital-twins/how-to-authenticate-client.md
@@ -17,7 +17,7 @@ ms.service: azure-digital-twins
 
 # Write client app authentication code
 
-After you [set up an Azure Digital Twins instance and authentication](how-to-set-up-instance-portal.md), create a client application to interact with the instance. After you set up a starter client project, **write code in that client app to authenticate it** against the Azure Digital Twins instance.
+After you [set up an Azure Digital Twins instance and authentication](how-to-set-up-instance-portal.md), you can create a client application to interact with the instance. This article explains how to **write code in that client app to authenticate it** against the Azure Digital Twins instance.
 
 Azure Digital Twins authenticates using [Microsoft Entra Security Tokens based on OAUTH 2.0](../active-directory/develop/security-tokens.md#json-web-tokens-and-claims). To authenticate your SDK, get a bearer token with the right permissions to Azure Digital Twins, and pass it along with your API calls.
 
@@ -35,14 +35,14 @@ To continue, you need a client app project in which you write your code. If you
 
 * [.NET (C#)](/dotnet/api/azure.identity?view=azure-dotnet&preserve-view=true)
 * [Java](/java/api/overview/azure/identity-readme?view=azure-java-stable&preserve-view=true)
-* [JavaScript](/JavaScript/api/overview/azure/identity-readme?view=azure-node-latest&preserve-view=true)
+* [JavaScript](/javascript/api/overview/azure/identity-readme?view=azure-node-latest&preserve-view=true)
 * [Python](/python/api/overview/azure/identity-readme?view=azure-python&preserve-view=true)
 
 Three common credential-obtaining methods in `Azure.Identity` are:
 
-* [DefaultAzureCredential](/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet&preserve-view=true) provides a default `TokenCredential` authentication flow for applications that are deployed to Azure. This method is **the recommended choice for local development**. It also tries the other two methods recommended in this article; it wraps `ManagedIdentityCredential` and can access `InteractiveBrowserCredential` with a configuration variable.
+* [DefaultAzureCredential](/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet&preserve-view=true) provides a default `TokenCredential` authentication flow for applications that are deployed to Azure. This method is **the recommended choice for local development**. It's also capable of trying the other two methods recommended in this article; it wraps `ManagedIdentityCredential` and can access `InteractiveBrowserCredential` with a configuration variable.
 * [ManagedIdentityCredential](/dotnet/api/azure.identity.managedidentitycredential?view=azure-dotnet&preserve-view=true) works well in cases where you need [managed identities (MSI)](../active-directory/managed-identities-azure-resources/overview.md). This method is a good candidate for working with Azure Functions and deploying to Azure services.
-* [InteractiveBrowserCredential](/dotnet/api/azure.identity.interactivebrowsercredential?view=azure-dotnet&preserve-view=true) is intended for interactive applications. Use this method to create an authenticated SDK client.
+* [InteractiveBrowserCredential](/dotnet/api/azure.identity.interactivebrowsercredential?view=azure-dotnet&preserve-view=true) is intended for interactive applications. This is one method of creating an authenticated SDK client.
 
 The rest of this article shows how to use these methods with the [.NET (C#) SDK](/dotnet/api/overview/azure/digitaltwins.core-readme).
 
@@ -78,7 +78,7 @@ Here's a code sample to add a `DefaultAzureCredential` to your project:
 
 The [ManagedIdentityCredential](/dotnet/api/azure.identity.managedidentitycredential?view=azure-dotnet&preserve-view=true) method works well in cases where you need [managed identities (MSI)](../active-directory/managed-identities-azure-resources/overview.md)—for example, when [authenticating with Azure Functions](#authenticate-azure-functions).
 
-This method means that you can use `ManagedIdentityCredential` in the same project as `DefaultAzureCredential` or `InteractiveBrowserCredential` to authenticate a different part of the project.
+You can use `ManagedIdentityCredential` in the same project as `DefaultAzureCredential` or `InteractiveBrowserCredential` to authenticate a different part of the project.
 
 To use the default Azure credentials, you need the Azure Digital Twins instance's URL ([instructions to find](how-to-set-up-instance-portal.md#verify-success-and-collect-important-values)). You might also need an [app registration](./how-to-create-app-registration.md) and the registration's [Application (client) ID](./how-to-create-app-registration.md#collect-client-id-and-tenant-id).
 
@@ -126,7 +126,7 @@ When writing the Azure function, consider adding these variables and code to you
 
     :::code language="csharp" source="~/digital-twins-docs-samples/sdks/csharp/adtIngestFunctionSample.cs" id="ManagedIdentityCredential":::
 
-When you create the credential without parameters, as shown in the previous example, it returns the credential for the function app's system-assigned identity, if it has one. To specify a user-assigned identity instead, pass the user-assigned identity's **client ID** into the `id` parameter for the constructor.   
+    When you create the credential without parameters, as shown in the previous example, it returns the credential for the function app's system-assigned identity, if it has one. To specify a user-assigned identity instead, pass the user-assigned identity's **client ID** into the `id` parameter for the constructor.   
 
     Later, after publishing the function, ensure that the function's identity has permission to access the Azure Digital Twins APIs. For instructions on how to do so, see [Assign an access role](#assign-an-access-role).    
 
diff --git a/articles/digital-twins/how-to-create-endpoints.md b/articles/digital-twins/how-to-create-endpoints.md
@@ -31,7 +31,7 @@ Routing [event notifications](concepts-event-notifications.md) from Azure Digita
     
     :::image type="content" source="media/includes/instance-details.png" alt-text="Screenshot of the Overview page for an Azure Digital Twins instance in the Azure portal. The name and resource group are highlighted." lightbox="media/includes/instance-details.png":::
 
-Next, follow the instructions in the following section if you intend to use the Azure CLI while following this guide.
+If you intend to use the Azure CLI while following this guide, follow the instructions in the next section.
 
 [!INCLUDE [azure-cli-prepare-your-environment-h3.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-h3.md)]
 
@@ -116,7 +116,7 @@ The rest of this section walks through three steps for setting up an endpoint wi
 
 ### 1. Enable managed identity for the instance
 
-Use the tabs for instructions that match your preferred experience.
+Use the following tabs for instructions that match your preferred experience.
 
 # [Portal](#tab/portal) 
 
@@ -147,7 +147,7 @@ Here are the minimum roles that your Azure Digital Twins identity needs to acces
 | Azure Service Bus | Azure Service Bus Data Sender |
 | Azure storage container | Storage Blob Data Contributor |
 
-Use the tabs to assign the role using your preferred experience.
+Use the following tabs to assign the role using your preferred experience.
 
 # [Portal](#tab/portal) 
 
@@ -245,7 +245,7 @@ To learn more about dead-lettering, see [Endpoints and event routes](concepts-ro
 
 Before setting the dead-letter location, you must have a [storage account](../storage/common/storage-account-create.md?tabs=azure-portal) with a [container](../storage/blobs/storage-quickstart-blobs-portal.md#create-a-container) in your Azure account. 
 
-Provide the URI for this container when creating the endpoint. The dead-letter location is provided to the endpoint as a container URI with a [SAS token](../storage/common/storage-sas-overview.md). That token needs `write` permission for the destination container within the storage account. The fully formed dead letter SAS URI is in the format of: `https://<storage-account-name>.blob.core.windows.net/<container-name>?<SAS-token>`.
+When creating the endpoint, you provide the URI of this container. The dead-letter location is provided to the endpoint as a container URI with a [SAS token](../storage/common/storage-sas-overview.md). That token needs `write` permission for the destination container within the storage account. The fully formed dead letter SAS URI is in the format of: `https://<storage-account-name>.blob.core.windows.net/<container-name>?<SAS-token>`.
 
 To set up these storage resources in your Azure account, follow the steps in the following section. After setting up the storage resources, you can set up the endpoint connection.
 
@@ -288,9 +288,9 @@ Next, create a SAS token for your storage account that the endpoint can use to a
     The output of this command is the SAS token. Copy the SAS token value to use later.
 
     > [!NOTE]
-> This command includes "**b**lob", "**f**ile", "**q**ueue", and "**t**able" *services*; an "**o**bject" *resource type*; and allows "**w**rite" *permissions*.
-> 
-> For more information about the `az storage account generate-sas` command and its parameters, see the [Azure CLI reference](/cli/azure/storage/account#az-storage-account-generate-sas).
+    > This command includes "**b**lob", "**f**ile", "**q**ueue", and "**t**able" *services*; an "**o**bject" *resource type*; and allows "**w**rite" *permissions*.
+    > 
+    > For more information about the `az storage account generate-sas` command and its parameters, see the [Azure CLI reference](/cli/azure/storage/account#az-storage-account-generate-sas).
 
 ---
 
diff --git a/articles/iot-operations/get-started-end-to-end-sample/quickstart-get-insights.md b/articles/iot-operations/get-started-end-to-end-sample/quickstart-get-insights.md
@@ -1,6 +1,6 @@
 ---
 title: "Quickstart: Get insights from your processed data"
-description: "Quickstart: Use a Real-Time Dashboard to capture insights from the OPC UA data you sent to Event Hubs."
+description: "Quickstart: Use a real-time dashboard to capture insights from the OPC UA data you sent to Event Hubs."
 author: baanders
 ms.author: baanders
 ms.topic: quickstart
@@ -13,21 +13,21 @@ ms.date: 01/28/2025
 
 # Quickstart: Get insights from your processed data
 
-In this quickstart, you populate a [Real-Time Dashboard](/fabric/real-time-intelligence/dashboard-real-time-create) to capture insights from the OPC UA data that you sent to Event Hubs in the previous quickstart. Using Microsoft Fabric Real-Time Intelligence, you bring your data from Event Hubs into Microsoft Fabric, and map it into a KQL database that can be a source for Real-Time Dashboards. Then, you build a dashboard to display that data in visual tiles that capture insights and show the values over time.
+In this quickstart, you populate a [real-time dashboard](/fabric/real-time-intelligence/dashboard-real-time-create) to capture insights from the OPC UA data that you sent to Event Hubs in the previous quickstart. Using Microsoft Fabric Real-Time Intelligence, you bring your data from Event Hubs into Microsoft Fabric, and map it into a KQL database that can be a source for real-time dashboards. Then, you build a dashboard to display that data in visual tiles that capture insights and show the values over time.
 
 These operations are the last steps in the sample end-to-end quickstart experience, which goes from deploying Azure IoT Operations at the edge through getting insights from that device data in the cloud.
 
 ## Prerequisites
 
 Before you begin this quickstart, complete the previous Azure IoT Operations quickstarts.
 
-You also need to meet the following Fabric requirements:
+You also need to have the following Fabric resources:
 * A Microsoft Fabric subscription. In your subscription, you need access to a workspace with **Contributor** or above permissions.
-* A Fabric tenant that allows the creation of Real-Time Dashboards. Your tenant administrator can enable this setting. For more information, see [Enable tenant settings in the admin portal](/fabric/real-time-intelligence/dashboard-real-time-create#enable-tenant-settings-in-the-admin-portal).
+* A Fabric tenant that allows the creation of real-time dashboards. Your tenant administrator can enable this setting. For more information, see [Enable tenant settings in the admin portal](/fabric/real-time-intelligence/dashboard-real-time-create#enable-tenant-settings-in-the-admin-portal).
 
 ## What problem will we solve?
 
-When your OPC UA data arrives in the cloud, there's a lot of information available to analyze. You might want to organize that data and create reports containing graphs and visualizations to derive insights from the data. The steps in this quickstart illustrate how to connect that data to Real-Time Intelligence and create a Real-Time Dashboard.
+When your OPC UA data arrives in the cloud, there's a lot of information available to analyze. You might want to organize that data and create reports containing graphs and visualizations to derive insights from the data. The steps in this quickstart illustrate how to connect that data to Real-Time Intelligence and create a real-time dashboard.
 
 ## Ingest data into Real-Time Intelligence
 
@@ -44,7 +44,7 @@ Add your event hub as a data source for a new eventstream. For detailed instruct
 * Edit the **Eventstream name** to something friendly in the **Stream details** pane.
 * For **Azure Event Hub Key**, use the default selection (*RootManageSharedAccessKey*).
 * For **Connection**, create a new connection with Shared Access Key authentication. The connection credential details fill automatically.
-    * Make sure local authentication is enabled on your Event Hubs namespace. You can set this authentication from the Overview page of the Azure portal.
+    * Make sure local authentication is enabled on your Event Hubs namespace. You can set this authentication from the namespace's Overview page in the Azure portal.
 * For **Consumer group**, use the default selection (*$Default*).
 * For **Data format**, use the default selection (*Json*).
 
@@ -79,7 +79,7 @@ In this section, you create a KQL database in your Microsoft Fabric workspace to
     | Spike | bool |
     | Temperature | decimal |
     | FillWeight | decimal |
-| EnergyUse | decimal |
+    | EnergyUse | decimal |
     | Timestamp | datetime |
 
 1. After you create the *OPCUA* table, select it and use the **Query with code** button to open any sample query in a new query window for the table.
@@ -124,8 +124,8 @@ Navigate to your workspace and create a new real-time dashboard from the Real-Ti
 
 Download the sample dashboard template from this location in GitHub: [dashboard-AIOquickstart.json](https://github.com/Azure-Samples/explore-iot-operations/blob/main/samples/dashboard/dashboard-AIOquickstart.json).
 
-Then, follow the steps to upload the dashboard template and connect it to your data.
-1. In your Real-Time Dashboard, switch to the **Manage** tab and select **Replace with file**.
+Then, follow these steps to upload the dashboard template and connect it to your data.
+1. In your real-time dashboard, switch to the **Manage** tab and select **Replace with file**.
     :::image type="content" source="media/quickstart-get-insights/dashboard-upload-replace.png" alt-text="Screenshot of the buttons to upload a file template.":::
 1. Select the template file that you downloaded to your machine.
 1. The template file populates the dashboard with multiple tiles, although the tiles can't get data because you haven't connected a data source yet.
@@ -164,4 +164,4 @@ Now that you're finished with the quickstart experience, this section contains i
 > [!NOTE]
 > The resource group contains the Event Hubs namespace you created in this quickstart.
 
-You can also delete your Microsoft Fabric workspace and all the resources within it associated with this quickstart, including the eventstream, Eventhouse, and Real-Time Dashboard. Additionally, you might want to delete the dashboard template file that you downloaded to your computer.
+You can also delete your Microsoft Fabric workspace and all the resources within it associated with this quickstart, including the eventstream, Eventhouse, and real-time dashboard. Additionally, you might want to delete the dashboard template file that you downloaded to your computer.
