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

rolyon · rolyon · commit 7cfefdac45bb · 2024-09-10T15:21:01.000-07:00
diff --git a/articles/azure-functions/functions-bindings-event-grid-trigger.md b/articles/azure-functions/functions-bindings-event-grid-trigger.md
@@ -489,7 +489,7 @@ For explanations of the common and event-specific properties, see [Event propert
 
 ## Next steps
 
-* If you have questions, submit an issue to the team [here](https://github.com/Azure/azure-functions-eventgrid-extension/issues)
+* If you have questions, submit an issue to the team [here](https://github.com/Azure/azure-sdk-for-net/issues)
 * [Dispatch an Event Grid event](./functions-bindings-event-grid-output.md)
 
 [EventGridEvent]: /dotnet/api/microsoft.azure.eventgrid.models.eventgridevent
diff --git a/articles/cost-management-billing/reservations/reservation-discount-databricks.md b/articles/cost-management-billing/reservations/reservation-discount-databricks.md
@@ -1,16 +1,16 @@
 ---
-title: How an Azure Databricks prepurchase discount is applied
-description: Learn how an Azure Databricks prepurchase discount applies to your usage. You can use Databricks prepurchased units at any time during the purchase term.
+title: How an Azure Databricks pre-purchase discount is applied
+description: Learn how an Azure Databricks pre-purchase discount applies to your usage. You can use Databricks prepurchased units at any time during the purchase term.
 author: bandersmsft
 ms.reviewer: primittal
 ms.service: cost-management-billing
 ms.subservice: reservations
 ms.topic: conceptual
-ms.date: 05/07/2024
+ms.date: 09/10/2024
 ms.author: banders
 ---
 
-# How Azure Databricks prepurchase discount is applied
+# How Azure Databricks pre-purchase discount is applied
 
 You can use prepurchased Azure Databricks commit units (DBCU) at any time during the purchase term. Any Azure Databricks usage is deducted from the prepurchased DBCUs automatically.
 
@@ -20,25 +20,10 @@ The prepurchase discount applies only to Azure Databricks unit (DBU) usage. Othe
 
 ## Prepurchase discount application
 
-Databricks prepurchase applies to all Databricks workloads and tiers. You can think of the prepurchase as a pool of prepaid Databricks commit units. Usage is deducted from the pool, regardless of the workload or tier. Usage is deducted in the following ratios:
-
-| Workload | DBU application ratio - Standard tier | DBU application ratio - Premium tier |
-| --- | --- | --- |
-| All-purpose compute | 0.4 | 0.55 |
-| Jobs compute | 0.15 | 0.30 |
-| Jobs light compute | 0.07 | 0.22 |
-| SQL compute | N/A | 0.22 |
-| SQL Pro compute | N/A | 0.55 |
-| Serverless SQL | N/A | 0.70 |
-| Serverless real-time inference | N/A | 0.082 |
-| Model training | N/A | 0.65 |
-| Delta Live Tables | NA | 0.30 (core), 0.38 (pro), 0.54 (advanced) |
-| All Purpose Photon | NA | 0.55 |
-
-For example, when All-purpose compute – Standard Tier capacity gets consumed, the prepurchased Databricks commit units get deducted by 0.4 units. When Jobs light compute – Standard Tier capacity gets used, the prepurchased Databricks commit unit gets deducted by 0.07 units.
+Databricks pre-purchase applies to all Databricks workloads and tiers. You can think of the prepurchase as a pool of prepaid Databricks commit units. 
 
 >[!NOTE]
-> Enabling Photon increases the DBU count.
+> Usage is deducted from the pool, regardless of the workload or tier. Usage is deducted at various rates, depending on the workload and tier. For more information and a complete list of rates, see the [Databricks pricing page](https://azure.microsoft.com/pricing/details/databricks/).
 
 ## Determine plan use
 
diff --git a/articles/cost-management-billing/reservations/synapse-analytics-pre-purchase-plan.md b/articles/cost-management-billing/reservations/synapse-analytics-pre-purchase-plan.md
@@ -6,7 +6,7 @@ ms.reviewer: primittal
 ms.service: cost-management-billing
 ms.subservice: reservations
 ms.topic: how-to
-ms.date: 04/15/2024
+ms.date: 09/10/2024
 ms.author: banders
 ---
 
@@ -71,12 +71,13 @@ You can't split or merge a Synapse Pre-Purchase Plan. For more information about
 
 Cancel and exchange isn't supported for Synapse Pre-Purchase Plans. All purchases are final.
 
-## Next steps
+## Related content
 
 To learn more about Azure Reservations, see the following articles:
 
 - [What are Azure Reservations?](save-compute-costs-reservations.md)
 - [Manage Azure Reservations](manage-reserved-vm-instance.md)
 - [Understand Azure Reservations discount](understand-reservation-charges.md)
-- [Understand reservation usage for your Pay-As-You-Go subscription](understand-reserved-instance-usage.md)
+- [Understand reservation usage for your pay-as-you-go subscription](understand-reserved-instance-usage.md)
 - [Understand reservation usage for your Enterprise enrollment](understand-reserved-instance-usage-ea.md)
+- [Buy a reservation](prepare-buy-reservation.md)
diff --git a/articles/load-balancer/egress-only.md b/articles/load-balancer/egress-only.md
@@ -31,7 +31,7 @@ This configuration provides outbound NAT for an internal load balancer scenario,
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
-[!INCLUDE [load-balancer-create-bastion](../../includes/load-balancer-create-bastion.md)]
+[!INCLUDE [load-balancer-create-bastion-no-natgateway](../../includes/load-balancer-create-bastion-no-natgateway.md)]
 
 ## Create internal load balancer
 
diff --git a/articles/virtual-network/ip-services/media/default-outbound-access/edit-subnet-window-no-nat.png b/articles/virtual-network/ip-services/media/default-outbound-access/edit-subnet-window-no-nat.png
diff --git a/includes/azure-storage-account-metrics-dimensions.md b/includes/azure-storage-account-metrics-dimensions.md
@@ -9,7 +9,7 @@
 | **Dimension Name** | **Description** |
 | ------------------- | ----------------- |
 | **GeoType** | Transaction from Primary or Secondary cluster. The available values include **Primary** and **Secondary**. It applies to Read Access Geo Redundant Storage (RA-GRS) when reading objects from a secondary tenant. |
-| **ResponseType** | Transaction response type. The available values include: <br/><br/> <li>**ServerOtherError**: All other server-side errors except described ones. </li> <li>**ServerBusyError**: Authenticated request that returned an HTTP 503 status code. </li> <li>**ServerTimeoutError**: Timed-out authenticated request that returned an HTTP 500 status code. The timeout occurred due to a server error. </li><li>**AuthenticationError**: The request couldn't be authenticated by the server.</li><li>**AuthorizationError**: Authenticated request that failed due to unauthorized access of data or an authorization failure. </li> <li>**NetworkError**: Authenticated request that failed due to network errors. Most commonly occurs when a client prematurely closes a connection before timeout expiration. </li><li>**ClientAccountBandwidthThrottlingError**: The request is throttled on bandwidth for exceeding [storage account scalability limits](../articles/storage/common/scalability-targets-standard-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json).</li><li>**ClientAccountRequestThrottlingError**: The request is throttled on request rate for exceeding [storage account scalability limits](../articles/storage/common/scalability-targets-standard-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json).<li>**ClientThrottlingError**: Other client-side throttling error. `ClientAccountBandwidthThrottlingError` and `ClientAccountRequestThrottlingError` are excluded.</li><li>**ClientShareEgressThrottlingError**: Applicable to premium file shares only. Other client-side throttling error. The request failed due to egress bandwidth throttling for exceeding share limits. `ClientAccountBandwidthThrottlingError` is excluded.</li><li>**ClientShareIngressThrottlingError**: Applicable to premium file shares only. Other client-side throttling error. The request failed due to ingress bandwidth throttling for exceeding share limits. `ClientAccountBandwidthThrottlingError` is excluded.</li><li>**ClientShareIopsThrottlingError**: Other client-side throttling error. The request failed due to IOPS throttling. `ClientAccountRequestThrottlingError` is excluded.</li><li>**ClientTimeoutError**: Timed-out authenticated request that returned an HTTP 500 status code. If the client's network timeout or the request timeout is set to a lower value than expected by the storage service, it's an expected timeout. Otherwise, it's reported as a `ServerTimeoutError`. </li> <li>**ClientOtherError**: All other client-side errors except described ones. </li> <li>**Success**: Successful request</li> <li> **SuccessWithThrottling**: Successful request when an SMB client gets throttled in the first attempt(s) but succeeds after retries.</li><li> **SuccessWithShareEgressThrottling**: Applicable to premium file shares only. Successful request when an SMB client gets throttled due to egress bandwidth throttling in the first attempt or attempts, but succeeds after retries.</li><li> **SuccessWithShareIngressThrottling**: Applicable to premium file shares only. Successful request when an SMB client gets throttled due to ingress bandwidth throttling in the first attempt or attempts, but succeeds after retries.</li><li> **SuccessWithShareIopsThrottling**: Successful request when an SMB client gets throttled due to IOPS throttling in the first attempt(s) but succeeds after retries.</li><li> **SuccessWithMetadataWarning**: Applicable to premium file shares only. Successful request when a client runs high metadata IOPS, which may cause throttling later if the IOPS remain high or increase.</li><li> **SuccessWithMetadataThrottling**: Applicable to premium file shares only. Successful request when a client gets throttled due to high metadata IOPS in the first attempt or attempts, but succeeds after retries.</li> |
+| **ResponseType** | Transaction response type. The available values include: <br/><br/> <li>**ServerOtherError**: All other server-side errors except described ones. </li> <li>**ServerBusyError**: Authenticated request that returned an HTTP 503 status code. </li> <li>**ServerTimeoutError**: Timed-out authenticated request that returned an HTTP 500 status code. The timeout occurred due to a server error. </li><li>**AuthenticationError**: The request couldn't be authenticated by the server.</li><li>**AuthorizationError**: Authenticated request that failed due to unauthorized access of data or an authorization failure. </li> <li>**NetworkError**: Authenticated request that failed due to network errors. Most commonly occurs when a client prematurely closes a connection before timeout expiration. </li><li>**ClientAccountBandwidthThrottlingError**: The request is throttled on bandwidth for exceeding [storage account scalability limits](../articles/storage/common/scalability-targets-standard-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json).</li><li>**ClientAccountRequestThrottlingError**: The request is throttled on request rate for exceeding [storage account scalability limits](../articles/storage/common/scalability-targets-standard-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json).<li>**ClientThrottlingError**: Other client-side throttling error. `ClientAccountBandwidthThrottlingError` and `ClientAccountRequestThrottlingError` are excluded.</li><li>**ClientShareEgressThrottlingError**: Applicable to premium file shares only. Other client-side throttling error. The request failed due to egress bandwidth throttling for exceeding share limits. `ClientAccountBandwidthThrottlingError` is excluded.</li><li>**ClientShareIngressThrottlingError**: Applicable to premium file shares only. Other client-side throttling error. The request failed due to ingress bandwidth throttling for exceeding share limits. `ClientAccountBandwidthThrottlingError` is excluded.</li><li>**ClientShareIopsThrottlingError**: Other client-side throttling error. The request failed due to IOPS throttling. `ClientAccountRequestThrottlingError` is excluded.</li><li>**ClientTimeoutError**: Timed-out authenticated request that returned an HTTP 500 status code. If the client's network timeout or the request timeout is set to a lower value than expected by the storage service, it's an expected timeout. Otherwise, it's reported as a `ServerTimeoutError`. </li> <li>**ClientOtherError**: All other client-side errors except described ones. </li> <li>**Success**: Successful request</li> <li> **SuccessWithThrottling**: Successful request when an SMB client gets throttled in the first attempt(s) but succeeds after retries.</li><li> **SuccessWithShareEgressThrottling**: Applicable to premium file shares only. Successful request when an SMB client gets throttled due to egress bandwidth throttling in the first attempt or attempts, but succeeds after retries.</li><li> **SuccessWithShareIngressThrottling**: Applicable to premium file shares only. Successful request when an SMB client gets throttled due to ingress bandwidth throttling in the first attempt or attempts, but succeeds after retries.</li><li> **SuccessWithShareIopsThrottling**: Successful request when an SMB client gets throttled due to IOPS throttling in the first attempt(s) but succeeds after retries.</li><li> **SuccessWithMetadataWarning**: Applicable to file shares only. Successful request when a client runs high metadata IOPS, which may cause throttling later if the IOPS remain high or increase.</li><li> **SuccessWithMetadataThrottling**: Applicable to file shares only. Successful request when a client gets throttled due to high metadata IOPS in the first attempt or attempts, but succeeds after retries.</li> |
 | **ApiName** | The name of operation. If a failure occurs before the name of the [operation](/rest/api/storageservices/storage-analytics-logged-operations-and-status-messages) is identified,  the name appears as "Unknown." You can use the value of the `ResponseType` dimension to learn more about the failure.
 | **Authentication** | Authentication type used in transactions. The available values include: <br/> <li>**AccountKey**: The transaction is authenticated with storage account key.</li> <li>**SAS**: The transaction is authenticated with service/account shared access signatures.</li><li>**DelegationSas**: The transaction is authenticated with user-delegation SAS.</li> <li>**OAuth**: The transaction is authenticated with OAuth access tokens.</li> <li>**Anonymous**: The transaction is requested anonymously. It doesn’t include preflight requests.</li> <li>**AnonymousPreflight**: The transaction is preflight request.</li>|
 | **TransactionType** | Type of transaction. The available values include: <br/> <li>**User**: The transaction was made by customer.</li> <li>**System**: The transaction was made by system process.</li> |
diff --git a/includes/load-balancer-create-bastion-no-natgateway.md b/includes/load-balancer-create-bastion-no-natgateway.md
@@ -0,0 +1,67 @@
+---
+ title: include file
+ description: include file
+ services: load-balancer
+ author: mbender-ms
+ ms.service: azure-load-balancer
+ ms.topic: include
+ ms.date: 11/29/2023
+ ms.author: mbender
+ ms.custom: include file
+---
+
+## Create a virtual network and bastion host
+
+In this section, you create a virtual network with a resource subnet, an Azure Bastion subnet, and an Azure Bastion host.
+
+> [!IMPORTANT]
+> [!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]
+
+1. In the portal, search for and select **Virtual networks**.
+
+2. On the **Virtual networks** page, select **+ Create**.
+
+3. On the **Basics** tab of **Create virtual network**, enter or select the following information:
+
+    | Setting | Value |
+    |---|---|
+    | **Project details** |  |
+    | Subscription | Select your subscription. |
+    | Resource group | Select **load-balancer-rg** from the dropdown or **Create new** if it doesn't exist.</br> Enter **load-balancer-rg** in Name.</br> Select **OK**. |
+    | **Instance details** |  |
+    | Name | Enter **lb-vnet**. |
+    | Region | Select **(US) East US**. |
+
+    :::image type="content" source="./media/load-balancer-internal-create-bastion-include/create-virtual-network-basics.png" alt-text="Screenshot of Basics tab of Create virtual network in the Azure portal.":::
+
+4. Select the **Security** tab or **Next** button at the bottom of the page.
+5. Under **Azure Bastion**, enter or select the following information:
+
+    | Setting | Value |
+    |---|---|
+    | **Azure Bastion** |  |
+    | Enable Azure Bastion | Select checkbox. |
+    | Azure Bastion host name | Enter **lb-bastion**. |
+    | Azure Bastion public IP address | Select **Create new**.</br> Enter **lb-bastion-ip** in Name.</br> Select **OK**. |
+
+6. Select the **IP addresses** tab, or **Next** at the bottom of the page.
+7. On **Create virtual network** page, enter or select the following information:
+
+    | Setting | Value |
+    |---|---|
+    | **Add IPv4 address space** |  |
+    | IPv4 address space | Enter **10.0.0.0/16 (65,356 addresses)**. |
+    | **Subnets** | Select the **default** subnet link to edit.  |
+    | **Edit subnet** | |
+    | Subnet purpose | Leave the default **Default**. |
+    | Name | Enter **backend-subnet**. |
+    | Starting address | Enter **10.0.0.0**. |
+    | Subnet size | Enter **/24(256 addresses)**. |
+    | **Security** |   |
+    | NAT Gateway | Select **None**. |
+
+    :::image type="content" source="./media/load-balancer-internal-create-bastion-include/edit-subnet-window.png" alt-text="Screenshot of default subnet rename and configuration.":::
+
+8. Select **Save**.
+
+9. Select **Review + create** at the bottom of the screen, and when validation passes, select **Create**.
