Merge pull request #253106 from MicrosoftDocs/main

9/27 OOB Publish at 6PM

Author: huypub

.openpublishing.redirection.active-directory.json

@@ -5460,6 +5460,11 @@
       "redirect_url": "/azure/active-directory/fundamentals/concept-fundamentals-security-defaults",
       "redirect_document_id": true
     },
+    {
+      "source_path_from_root": "/articles/active-directory/reports-monitoring/reference-azure-ad-sla-performance.md",
+      "redirect_url": "/azure/active-directory/reports-monitoring/reference-sla-performance",
+      "redirect_document_id": true
+    },
     {
       "source_path_from_root": "/articles/active-directory/reports-monitoring/quickstart-filter-audit-log.md",
       "redirect_url": "/azure/active-directory/reports-monitoring/howto-customize-filter-logs",

articles/active-directory/reports-monitoring/reference-azure-ad-sla-performance.md renamed to articles/active-directory/reports-monitoring/reference-sla-performance.md

@@ -1,18 +1,17 @@
 ---
 title: Microsoft Entra SLA performance
-description: Learn about the Microsoft Entra SLA performance
+description: Learn about the Microsoft Entra service level performance and attainment
 services: active-directory
 author: shlipsey3
 manager: amycolannino
 ms.service: active-directory
 ms.topic: reference
 ms.workload: identity
 ms.subservice: report-monitor
-ms.date: 05/22/2023
+ms.date: 09/27/2023
 ms.author: sarahlipsey
-ms.reviewer: besiler
+ms.reviewer: egreenberg14
 
-ms.collection: M365-identity-device-management
 ---
 
 # Microsoft Entra SLA performance 

articles/azure-functions/dotnet-isolated-in-process-differences.md

@@ -49,7 +49,7 @@ Use the following table to compare feature and functional differences between th
 
 <sup>5</sup> ASP.NET Core types are not supported for .NET Framework.
 
-<sup>6</sup> The isolated worker model supports .NET 8 as a preview, currently for Linux applications only. .NET 8 is not yet available for the in-process model. See the [Azure Functions Roadmap Update post](https://aka.ms/azure-functions-dotnet-roadmap) for more information about .NET 8 plans.
+<sup>6</sup> The isolated worker model supports .NET 8 [as a preview](./dotnet-isolated-process-guide.md#preview-net-versions). For information about .NET 8 plans, including future options for the in-process model, see the [Azure Functions Roadmap Update post](https://aka.ms/azure-functions-dotnet-roadmap).
 
 [HttpRequest]: /dotnet/api/microsoft.aspnetcore.http.httprequest
 [IActionResult]: /dotnet/api/microsoft.aspnetcore.mvc.iactionresult

articles/azure-functions/dotnet-isolated-process-guide.md

@@ -664,6 +664,38 @@ After the debugger is attached, the process execution resumes, and you'll be abl
 
 Because your isolated worker process app runs outside the Functions runtime, you need to attach the remote debugger to a separate process. To learn more about debugging using Visual Studio, see [Remote Debugging](functions-develop-vs.md?tabs=isolated-process#remote-debugging).
 
+## Preview .NET versions
+
+Azure Functions currently can be used with the following preview versions of .NET:
+
+| Operating system | .NET preview version |
+| - | - |
+| Windows | .NET 8 Preview 7 | 
+| Linux | .NET 8 RC1 |
+
+### Using a preview .NET SDK
+
+To use Azure Functions with a preview version of .NET, you need to update your project by:
+
+1. Installing the relevant .NET SDK version in your development
+1. Changing the `TargetFramework` setting in your `.csproj` file
+
+When deploying to a function app in Azure, you also need to ensure that the framework is made available to the app. To do so on Windows, you can use the following CLI command. Replace `<groupName>` with the name of the resource group, and replace `<appName>` with the name of your function app. Replace `<framework>` with the appropriate version string, such as "v8.0".
+
+```azurecli
+az functionapp config set -g <groupName> -n <appName> --net-framework-version <framework>
+```
+
+### Considerations for using .NET preview versions
+
+Keep these considerations in mind when using Functions with preview versions of .NET: 
+
+If you author your functions in Visual Studio, you must use [Visual Studio Preview](https://visualstudio.microsoft.com/vs/preview/), which supports building Azure Functions projects with .NET preview SDKs. You should also ensure you have the latest Functions tools and templates. To update these, navigate to `Tools->Options`, select `Azure Functions` under `Projects and Solutions`, and then click the `Check for updates` button, installing updates as prompted.
+
+During the preview period, your development environment might have a more recent version of the .NET preview than the hosted service. This can cause the application to fail when deployed. To address this, you can configure which version of the SDK to use in [`global.json`](/dotnet/core/tools/global-json). First, identify which versions you have installed using `dotnet --list-sdks` and note the version that matches what the service supports. Then you can run `dotnet new globaljson --sdk-version <sdk-version> --force`, substituting `<sdk-version>` for the version you noted in the previous command. For example, `dotnet new globaljson --sdk-version dotnet-sdk-8.0.100-preview.7.23376.3 --force` will cause the system to use the .NET 8 Preview 7 SDK when building your project.
+
+Note that due to just-in-time loading of preview frameworks, function apps running on Windows may experience increased cold start times when compared against earlier GA versions.
+
 ## Next steps
 
 > [!div class="nextstepaction"]

articles/azure-monitor/logs/cost-logs.md

@@ -24,7 +24,7 @@ The default pricing for Log Analytics is a pay-as-you-go model that's based on i
 
 ## Data size calculation
 
-Data volume is measured as the size of the data that will be stored in GB (10^9 bytes). The data size of a single record is calculated from a string representation of the columns that are stored in the Log Analytics workspace for that record. It doesn't matter whether the data is sent from an agent or added during the ingestion process. This calculation includes any custom columns added by the [logs ingestion API](logs-ingestion-api-overview.md), [transformations](../essentials/data-collection-transformations.md) or [custom fields](custom-fields.md) that are added as data is collected and then stored in the workspace.
+Data volume is measured as the size of the data sent to be stored and is measured in units of GB (10^9 bytes). The data size of a single record is calculated from a string representation of the columns that are stored in the Log Analytics workspace for that record. It doesn't matter whether the data is sent from an agent or added during the ingestion process. This calculation includes any custom columns added by the [logs ingestion API](logs-ingestion-api-overview.md), [transformations](../essentials/data-collection-transformations.md) or [custom fields](custom-fields.md) that are added as data is collected and then stored in the workspace.
 
 >[!NOTE]
 >The billable data volume calculation is generally substantially smaller than the size of the entire incoming JSON-packaged event. On average, across all event types, the billed size is around 25 percent less than the incoming data size. It can be up to 50 percent for small events. The percentage includes the effect of the standard columns excluded from billing. It's essential to understand this calculation of billed data size when you estimate costs and compare other pricing models.

articles/cosmos-db/.openpublishing.redirection.cosmos-db.json

@@ -6214,6 +6214,16 @@
       "source_path_from_root": "/articles/cosmos-db/rag-data-openai.md",
       "redirect_url": "/azure/cosmos-db/vector-search",
       "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/cosmos-db/gremlin/quickstart-java.md",
+      "redirect_url": "/azure/cosmos-db/gremlin/quickstart-console",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/cosmos-db/gremlin/quickstart-php.md",
+      "redirect_url": "/azure/cosmos-db/gremlin/quickstart-console",
+      "redirect_document_id": false
     }
   ]
 }

articles/cosmos-db/gremlin/TOC.yml

@@ -10,18 +10,14 @@
       href: gremlin-api-faq.yml
 - name: Quickstarts
   items:
-    - name: Gremlin console
+    - name: Console
       href: quickstart-console.md
-    - name: .NET
-      href: quickstart-dotnet.md
-    - name: Java
-      href: quickstart-java.md
-    - name: Node.js
-      href: quickstart-nodejs.md
     - name: Python
       href: quickstart-python.md
-    - name: PHP
-      href: quickstart-php.md
+    - name: Node.js
+      href: quickstart-nodejs.md
+    - name: .NET
+      href: quickstart-dotnet.md
 - name: Tutorials
   items:
     - name: Query data using Gremlin

articles/cosmos-db/gremlin/includes/create-account-database-graph-cli.md

@@ -0,0 +1,87 @@
+---
+author: seesharprun
+ms.author: sidandrews
+ms.service: cosmos-db
+ms.subservice: apache-gremlin
+ms.topic: include
+ms.date: 09/27/2023
+---
+
+1. Create shell variables for *accountName*, *resourceGroupName*, and *location*.
+
+    ```azurecli-interactive
+    # Variable for resource group name
+    resourceGroupName="msdocs-cosmos-gremlin-quickstart"
+    location="westus"
+    
+    # Variable for account name with a randomly generated suffix
+    
+    let suffix=$RANDOM*$RANDOM
+    accountName="msdocs-gremlin-$suffix"
+    ```
+
+1. If you haven't already, sign in to the Azure CLI using `az login`.
+
+1. Use `az group create` to create a new resource group in your subscription.
+
+    ```azurecli-interactive
+    az group create \
+        --name $resourceGroupName \
+        --location $location
+    ```
+
+1. Use `az cosmosdb create` to create a new API for NoSQL account with default settings.
+
+    ```azurecli-interactive
+    az cosmosdb create \
+        --resource-group $resourceGroupName \
+        --name $accountName \
+        --capabilities "EnableGremlin" \
+        --locations regionName=$location \
+        --enable-free-tier true
+    ```
+
+    > [!NOTE]
+    > You can have up to one free tier Azure Cosmos DB account per Azure subscription and must opt-in when creating the account. If this command fails to apply the free tier discount, this means another account in the subscription has already been enabled with free tier.
+
+1. Get the API for Gremlin endpoint *NAME* for the account using `az cosmosdb show`.
+
+    ```azurecli-interactive
+    az cosmosdb show \
+        --resource-group $resourceGroupName \
+        --name $accountName \
+        --query "name"
+    ```
+
+1. Find the *KEY* from the list of keys for the account with `az-cosmosdb-keys-list`.
+
+    ```azurecli-interactive
+    az cosmosdb keys list \
+        --resource-group $resourceGroupName \
+        --name $accountName \
+        --type "keys" \
+        --query "primaryMasterKey"
+    ```
+
+1. Record the *NAME* and *KEY* values. You use these credentials later.
+
+1. Create a *database* named `cosmicworks` using `az cosmosdb gremlin database create`.
+
+    ```azurecli-interactive
+    az cosmosdb gremlin database create \
+        --resource-group $resourceGroupName \
+        --account-name $accountName \
+        --name "cosmicworks"
+    ```
+
+1. Create a *graph* using `az cosmosdb gremlin graph create`. Name the graph `products`, then set the throughput to `400`, and finally set the partition key path to `/category`.
+
+    ```azurecli-interactive
+    az cosmosdb gremlin graph create \
+        --resource-group $resourceGroupName \
+        --account-name $accountName \
+        --database-name "cosmicworks" \
+        --name "products" \
+        --partition-key-path "/category" \
+        --throughput 400
+    ```

articles/cosmos-db/gremlin/includes/delete-account-cli.md

@@ -0,0 +1,17 @@
+---
+author: seesharprun
+ms.author: sidandrews
+ms.service: cosmos-db
+ms.subservice: apache-gremlin
+ms.topic: include
+ms.date: 09/27/2023
+---
+
+1. Open your terminal in any folder.
+
+1. Use `az group delete` to delete the resource group.
+
+    ```azurecli-interactive
+    az group delete \
+        --name $resourceGroupName
+    ```

articles/cosmos-db/gremlin/includes/quickstart-devlang.md

@@ -0,0 +1,16 @@
+---
+author: seesharprun
+ms.author: sidandrews
+ms.service: cosmos-db
+ms.subservice: apache-gremlin
+ms.topic: include
+ms.date: 09/27/2023
+---
+
+> [!div class="op_single_selector"]
+>
+> - [Console](../quickstart-console.md)
+> - [Python](../quickstart-python.md)
+> - [Node.js](../quickstart-nodejs.md)
+> - [.NET](../quickstart-dotnet.md)
+>