Skip to content

Commit 746ff75

Browse files
authored
Merge pull request #288684 from MicrosoftDocs/main
10/18 11:00 AM IST Publish
2 parents 2b5a66d + 8cdc16e commit 746ff75

File tree

79 files changed

+2486
-1208
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

79 files changed

+2486
-1208
lines changed

articles/api-management/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -151,8 +151,8 @@
151151
href: high-availability.md
152152
- name: Deploy to multiple Azure regions
153153
href: api-management-howto-deploy-multi-region.md
154-
- name: Enable zone redundancy
155-
displayName: Availability zones
154+
- name: Enable availability zones
155+
displayName: zonal, zone-redundant
156156
href: ../reliability/migrate-api-mgt.md?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json
157157
- name: Set up DR using backup/restore
158158
displayName: disaster, recovery

articles/api-management/api-management-howto-deploy-multi-region.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ When adding a region, you configure:
1919

2020
* The number of scale [units](upgrade-and-scale.md) that region will host.
2121

22-
* Optional [zone redundancy](../reliability/migrate-api-mgt.md), if that region supports it.
22+
* Optional [availability zones](../reliability/migrate-api-mgt.md), if that region supports it.
2323

2424
* [Virtual network](virtual-network-concepts.md) settings in the added region, if networking is configured in the existing region or regions.
2525

@@ -33,7 +33,7 @@ When adding a region, you configure:
3333
## Prerequisites
3434

3535
* If you haven't created an API Management service instance, see [Create an API Management service instance](get-started-create-service-instance.md). Select the Premium service tier.
36-
* If your API Management instance is deployed in a virtual network, ensure that you set up a virtual network and subnet in the location that you plan to add, and within the same subscription. To enable zone redundancy, also set up a new public IP. See [virtual network prerequisites](api-management-using-with-vnet.md#prerequisites).
36+
* If your API Management instance is deployed in a virtual network, ensure that you set up a virtual network and subnet in the location that you plan to add, and within the same subscription. See [virtual network prerequisites](api-management-using-with-vnet.md#prerequisites).
3737

3838
## <a name="add-region"> </a>Deploy API Management service to an additional region
3939

@@ -184,7 +184,7 @@ This section provides considerations for multi-region deployments when the API M
184184

185185
* Learn more about configuring API Management for [high availability](high-availability.md).
186186

187-
* Learn more about [zone redundancy](../reliability/migrate-api-mgt.md) to improve the availability of an API Management instance in a region.
187+
* Learn more about configuring [availability zones](../reliability/migrate-api-mgt.md) to improve the availability of an API Management instance in a region.
188188

189189
* For more information about virtual networks and API Management, see:
190190

articles/api-management/high-availability.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Enabling [zone redundancy](../reliability/migrate-api-mgt.md) for an API Managem
3636
When you enable zone redundancy in a region, consider the number of API Management scale [units](upgrade-and-scale.md) that need to be distributed. Minimally, configure the same number of units as the number of availability zones, or a multiple so that the units are distributed evenly across the zones. For example, if you select 3 availability zones in a region, you could have 3 units so that each zone hosts one unit.
3737

3838
> [!NOTE]
39-
> Use the [capacity](api-management-capacity.md) metric and your own testing to decide the number of scale units that will provide the gateway performance for your needs. Learn more about [scaling and upgrading](upgrade-and-scale.md) your service instance.
39+
> Use [capacity metrics](api-management-capacity.md) and your own testing to decide the number of scale units that will provide the gateway performance for your needs. Learn more about [scaling and upgrading](upgrade-and-scale.md) your service instance.
4040
4141
## Multi-region deployment
4242

articles/automation/delete-account.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article tells how to delete and your Automation account across
44
services: automation
55
ms.service: azure-automation
66
ms.subservice: process-automation
7-
ms.date: 09/09/2024
7+
ms.date: 10/10/2024
88
ms.topic: how-to
99
---
1010

@@ -103,11 +103,11 @@ To delete your Automation account linked to a Log Analytics workspace in support
103103

104104
1. Sign in to Azure at [https://portal.azure.com](https://portal.azure.com).
105105

106-
2. Navigate to your Automation account, and select **Linked workspace** under **Related resources**.
106+
1. Navigate to your Automation account, and select **Linked workspace**.
107107

108-
3. Select **Go to workspace**.
108+
1. Under **Related resources**, select **Linked workspace** and then select **Go to workspace**.
109109

110-
4. Select **Solutions** under **General**.
110+
4. Under **Classic**, select **Legacy solutions**.
111111

112112
5. On the Solutions page, select one of the following based on the feature(s) deployed in the account:
113113

Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
1+
---
2+
title: Save costs with reservations for Nutanix Cloud Clusters on Azure BareMetal infrastructure
3+
description: Save costs with Nutanix on Azure BareMetal reservations by committing to a reservation for your provisioned throughput units.
4+
author: bandersmsft
5+
ms.reviewer: primittal
6+
ms.service: cost-management-billing
7+
ms.subservice: reservations
8+
ms.topic: how-to
9+
ms.date: 10/16/2024
10+
ms.author: banders
11+
# customer intent: As a billing administrator, I want to learn about saving costs with Nutanix Cloud Clusters on Azure BareMetal Infrastructure Reservations and buy one.
12+
---
13+
14+
# Save costs with reservations for Nutanix Cloud Clusters on Azure BareMetal infrastructure
15+
16+
You can save money on [Nutanix Cloud Clusters (NC2) on Azure](../../baremetal-infrastructure/workloads/nc2-on-azure/nc2-baremetal-overview.md) with reservations. The reservation discount automatically applies to the running NC2 workload on Azure hosts that match the reservation scope and attributes. A reservation purchase covers only the compute part of your usage and doesn't include software licensing costs.
17+
18+
## Purchase restriction considerations
19+
20+
Reservations for NC2 on Azure BareMetal Infrastructure are available with some exceptions.
21+
22+
- **Clouds** - Reservations are available only in the regions listed on the [Supported instances and regions](../../baremetal-infrastructure/workloads/nc2-on-azure/supported-instances-and-regions.md) page.
23+
- **Capacity restrictions** - In rare circumstances, Azure limits the purchase of new reservations for NC2 on Azure host SKUs because of low capacity in a region.
24+
25+
## Reservation scope
26+
27+
When you purchase a reservation, you choose a scope that determines which resources get the reservation discount. A reservation applies to your usage within the purchased scope.
28+
29+
To choose a subscription scope, use the Scope list at the time of purchase. You can change the reservation scope after purchase.
30+
31+
- **Single resource group scope** - Applies the reservation discount to the matching resources in the selected resource group only.
32+
- **Single subscription scope** - Applies the reservation discount to the matching resources in the selected subscription.
33+
- **Shared scope** - Applies the reservation discount to matching resources in eligible subscriptions that are in the billing context. If a subscription is moved to different billing context, the benefit no longer applies to the subscription. It continues to apply to other subscriptions in the billing context.
34+
- For enterprise customers, the billing context is the EA enrollment. The reservation shared scope would include multiple Microsoft Entra tenants in an enrollment.
35+
- For Microsoft Customer Agreement customers, the billing scope is the billing profile.
36+
- For pay-as-you-go customers, the shared scope is all pay-as-you-go subscriptions created by the account administrator.
37+
- **Management group** - Applies the reservation discount to the matching resource in the list of subscriptions that are a part of both the management group and billing scope. The management group scope applies to all subscriptions throughout the entire management group hierarchy. To buy a reservation for a management group, you must have at least read permission on the management group and be a reservation owner or reservation purchaser on the billing subscription.
38+
39+
For more information on Azure reservations, see [What are Azure Reservations](save-compute-costs-reservations.md).
40+
41+
## Purchase requirements
42+
43+
To purchase reservation:
44+
45+
- You must be in the **Owner** role for at least one Enterprise or individual subscription with pay-as-you-go rates.
46+
- For Enterprise subscriptions, **Add Reserved Instances** must be enabled in the EA portal. Or, if that setting is disabled, you must be an EA Admin on the subscription.
47+
- For the Cloud Solution Provider (CSP) program, only admin agents or sales agents can buy an Azure Nutanix reservation.
48+
49+
## Purchase Nutanix on Azure BareMetal reservation
50+
51+
You can purchase a Nutanix on Azure BareMetal reservation through the [Azure portal](https://portal.azure.com/). You can pay for the reservation up front or with monthly payments. For more information about purchasing with monthly payments, see [Purchase Azure reservations with up front or monthly payments](prepare-buy-reservation.md).
52+
53+
To purchase reserved capacity:
54+
55+
1. Sign in to the [Azure portal](https://portal.azure.com/).
56+
2. Select **All services** > **Reservations** and then select **Nutanix on Azure BareMetal** to buy a new reservation.
57+
3. Select a subscription. Use the Subscription list to choose the subscription that gets used to pay for the reservation. The payment method of the subscription is charged the costs for the reservation. The subscription type must be an enterprise agreement (offer numbers: MS-AZR-0017P or MS-AZR-0148P), Microsoft Customer Agreement, or pay-as-you-go (offer numbers: MS-AZR-0003P or MS-AZR-0023P).
58+
1. For an enterprise subscription, the charges are deducted from the enrollment's Azure Prepayment (previously called monetary commitment) balance or charged as overage.
59+
2. For a pay-as-you-go subscription, the charges are billed to the credit card or invoice payment method on the subscription.
60+
4. Select a scope.
61+
5. Select AN36 or AN36P and select a region to choose an Azure region that gets covered by the reservation and select **Add to cart**.
62+
6. The number of instances to purchase within the reservation. The quantity is the number of running NC2 hosts that can get the billing discount.
63+
7. Select **Next: Review + Buy** and review your purchase choices and their prices.
64+
8. Select **Buy now**.
65+
9. After purchase, you can select **View this Reservation** to see your purchase status.
66+
67+
After you purchase a reservation, it gets applied automatically to any existing usage that matches the terms of the reservation.
68+
69+
## Usage data and reservation usage
70+
71+
Your usage that gets a reservation discount has an effective price of zero. You can see which NC2 instance received the reservation discount for each reservation.
72+
73+
For more information about how reservation discounts appear in usage data:
74+
75+
- For EA customers, see [Understand Azure reservation usage for your Enterprise enrollment](understand-reserved-instance-usage-ea.md)
76+
- For individual subscriptions, see [Understand Azure reservation usage for your pay-as-you-go subscription](understand-reserved-instance-usage.md)
77+
78+
## Exchange or refund a reservation
79+
80+
Exchange is allowed between NC2 AN36, AN36P, and AN64 SKUs. You can exchange or refund a reservation, with certain limitations. For more information about Azure Reservations policies, see [Self-service exchanges and refunds for Azure Reservations](exchange-and-refund-azure-reservations.md).
81+
82+
## Reservation expiration
83+
84+
When a reservation expires, any usage that you were covered under that reservation is billed at the pay-as-you go rate. Reservations are set to autorenewal on at time of purchase and you can choose to change the option as necessary at time of or after purchase.
85+
86+
An email notification is sent 30 days before the reservation expires, and again on the expiration date. To continue taking advantage of the cost savings that a reservation provides, renew it no later than the expiration date.
87+
88+
## Need help? Contact us
89+
90+
If you have questions or need help, [create a support request](https://go.microsoft.com/fwlink/?linkid=2083458).
91+
92+
## Related content
93+
94+
- To learn more about Azure reservations, see the following articles:
95+
- [What are Azure Reservations?](save-compute-costs-reservations.md)
96+
- [Manage Azure Reservations](manage-reserved-vm-instance.md)
97+
- [Understand Azure Reservations discount](understand-reservation-charges.md)

articles/cost-management-billing/reservations/prepare-buy-reservation.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,7 @@ You can purchase reservations from Azure portal, APIs, PowerShell, CLI. Read the
9494
- [Disk Storage](/azure/virtual-machines/disks-reserved-capacity)
9595
- [Microsoft Fabric](fabric-capacity.md)
9696
- [Microsoft Sentinel - Pre-Purchase](../../sentinel/billing-pre-purchase-plan.md?toc=/azure/cost-management-billing/reservations/toc.json)
97+
- [Nutanix on Azure BareMetal](nutanix-bare-metal.md)
9798
- [SAP HANA Large Instances](prepay-hana-large-instances-reserved-capacity.md)
9899
- [Software plans](/azure/virtual-machines/linux/prepay-suse-software-charges?toc=/azure/cost-management-billing/reservations/toc.json)
99100
- [SQL Database](/azure/azure-sql/database/reserved-capacity-overview?toc=/azure/cost-management-billing/reservations/toc.json)

articles/cost-management-billing/reservations/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -134,6 +134,8 @@
134134
href: fabric-capacity.md
135135
- name: Microsoft Sentinel - Pre-Purchase
136136
href: /azure/sentinel/billing-pre-purchase-plan?toc=/azure/cost-management-billing/reservations/toc.json
137+
- name: Nutanix on Azure BareMetal
138+
href: nutanix-bare-metal.md
137139
- name: SAP HANA Large Instances
138140
href: prepay-hana-large-instances-reserved-capacity.md
139141
- name: Software plans
Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
---
2+
title: Azure Health Data Services Availability Zones
3+
description: Overview of Availability Zones for Azure Health Data Services
4+
services: healthcare-apis
5+
author: expekesheth
6+
ms.service: azure-health-data-services
7+
ms.subservice: fhir
8+
ms.custom: devx-track-python
9+
ms.topic: conceptual
10+
ms.date: 10/15/2024
11+
ms.author: jasteppe
12+
---
13+
14+
# Availability Zones for Azure Health Data Services
15+
16+
The goal of high availability in Azure Health Data Services is to minimize impact on customer workloads from service maintenance operations and outages. Azure Health Data Services provides zone redundant availability using availability zones (AZs) for high availability and business continuity. To understand more about availability zones, visit [What are Azure availability zones?](/azure/reliability/availability-zones-overview?tabs=azure-cli).
17+
18+
Zone redundant availability provides resiliency by protecting against outages within a region. This is achieved using zone-redundant storage (ZRS), which replicates your data across three availability zones in the primary region. Each availability zone is a separate physical location with independent power, cooling, and networking. Zone redundant availability minimizes the risk of data loss if there are zone failures within the primary region.<br>
19+
For information on regions, see [Products availability by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
20+
21+
> [!NOTE]
22+
> Currently the availability zone feature is being provided to customers at no additional charge. In the future, charges will be incurred with the availability zone feature.
23+
24+
## Region availability
25+
26+
Here's a list of the availability zones for Azure Health Data Services.
27+
28+
- Australia East
29+
- Cental India
30+
- Japan East
31+
- Korea Central
32+
- Southeast Asia
33+
- France Central
34+
- North Europe
35+
- West Europe
36+
- UK South
37+
- Sweden Central
38+
- Germany West Central*
39+
- Qatar Central*
40+
- East US*
41+
- East US 2
42+
- South Central US*
43+
- West US 2*
44+
- West US 3*
45+
- Canada Central
46+
47+
Zones marked with a star ("*") have quota issues due to high demand. Enabling AZ features in these zones may take longer.
48+
49+
### Limitations
50+
51+
Consider the following limitations when configuring an availability zone.
52+
53+
- Azure Health Data Service FHIR&reg; service instances allow customers to set AZ settings only once and can't be modified.
54+
- FHIR service with data volume support beyond 4 TB needs to specify the AZ configuration during the service instance creation.
55+
- When this feature is available as self-serve, any FHIR service instance created in Azure Health Data Services needs to specify the AZ configuration during the service instance creation.
56+
57+
## Recovery Time Objective and Recovery Point Objective
58+
59+
The time required for an application to fully recover is known as the Recovery Time Objective (RTO). It's also the maximum period (time interval) of recent data updates the application can tolerate losing when recovering from an unplanned disruptive event.<br>
60+
The potential data loss is known as Recovery Point Objective (RPO).
61+
With zone redundant availability, Azure Health Data Services FHIR service provides an RTO of less than 10 minutes, and RPO of 0.
62+
63+
## Impact during zone-wide outages
64+
65+
During a zone-wide outage, no action is needed from the customer during zone recovery. Customers should be prepared to experience a brief interruption of communication to provisioned resources. Impact to regions due to a zone outage is communicated on [Azure status history](https://azure.status.microsoft/status/history/).
66+
67+
## Enabling an availability zone
68+
69+
To enable the availability zone on a specific instance, customers need to submit a support ticket with following details.
70+
71+
- Name of the subscription
72+
- Name of the FHIR service instance
73+
- Name of the resource group
74+
75+
More information can be found at [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request).
76+
77+
[!INCLUDE [FHIR trademark statement](includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/azure-api-for-fhir/release-notes.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,18 @@ ms.author: kavitagaddam
1717

1818
Azure API for FHIR&reg; provides a fully managed deployment of the Microsoft FHIR Server for Azure. The server is an implementation of the [FHIR](https://hl7.org/fhir) standard. This document provides details about the features and enhancements made to Azure API for FHIR.
1919

20+
## **October 2024**
21+
22+
### FHIR service
23+
24+
**Bug fixes**
25+
26+
- Export Validation: An issue was identified where exports proceeded despite invalid search parameters. We're introducing a change that prevents exports under these conditions. This feature is currently behind a strict validation flag and will become the default behavior on or after October 30.
27+
- Search Parameter Inclusion: We resolved an issue where additional search parameters (for instance, `_include`, `_has`) didn't return all expected results, sometimes omitting the next link.
28+
- Export Job Execution: A rare occurrence of `System.ObjectDisposedException` during export job completion has been addressed by preventing premature exits.
29+
- HTTP Status Code Update: The HTTP status code for invalid parameters during `$reindex` job creation is now updated to 400, ensuring better error handling.
30+
- Search Parameter Cleanup: A fix has been implemented to ensure complete cleanup of search parameters in the database when triggered with delete API calls, addressing issues related to incomplete deletions.
31+
2032
## **August 2024**
2133

2234
### FHIR service

articles/healthcare-apis/includes/rest-api-bundle-common.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,5 +76,5 @@ Transaction bundles don't support:
7676
Batch and transaction bundles are executed serially in the FHIR service. To improve performance and throughput, we enabled parallel processing of bundles.
7777

7878
To use parallel batch bundle processing:
79-
- Set header `x-bundle-processing-logic` value to 1parallel`.
79+
- Set header `x-bundle-processing-logic` value to `parallel`.
8080
- Ensure there's no overlapping resource ID that executes on DELETE, POST, PUT, or PATCH operations in the same bundle.

0 commit comments

Comments
 (0)