Skip to content

Commit a73a0e0

Browse files
authored
Merge pull request #278132 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 44a169f + 01115ef commit a73a0e0

File tree

4 files changed

+9
-9
lines changed

4 files changed

+9
-9
lines changed

articles/cost-management-billing/costs/allocate-costs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -132,12 +132,12 @@ The [Usage Details](/rest/api/consumption/usagedetails/list) API version `2021-1
132132

133133
However, cost allocation data results might be empty if you're using an unsupported API or if you don't have any cost allocation rules.
134134

135-
If you have cost allocation rules enabled, the `UnitPrice` field in your usage details file is 0. We recommend that you use price sheet data to get unit price information until it's available in the usage details file.
135+
If you have cost allocation rule(s) enabled, the unit price for the reserved instance (RI) purchase will show up as 0 in the usage details file. To work around this limitation, you could use the pricesheet data.
136136

137137
Cost allocation to a target doesn't happen if that target doesn't have any costs associated with it.
138138

139139
## Next steps
140140

141141
- Read the [Cost Management + Billing FAQ](../cost-management-billing-faq.yml) for questions and answers about cost allocation.
142142
- Create or update allocation rules using the [Cost allocation REST API](/rest/api/cost-management/costallocationrules)
143-
- Learn more about [How to optimize your cloud investment with Cost Management](cost-mgt-best-practices.md)
143+
- Learn more about [How to optimize your cloud investment with Cost Management](cost-mgt-best-practices.md)

articles/expressroute/about-fastpath.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,10 @@ ExpressRoute virtual network gateway is designed to exchange network routes and
1717

1818
### Circuits
1919

20-
FastPath is available on all ExpressRoute circuits. Limited general availability (GA) support for Private Endpoint/Private Link connectivity and Public preview support for virtual network peering and UDR connectivity over FastPath is only available for connections associated to ExpressRoute Direct circuits.
20+
FastPath is available on all ExpressRoute circuits. Limited general availability (GA) support for Private Endpoint/Private Link connectivity and support for virtual network peering and UDR connectivity over FastPath is only available for connections associated to ExpressRoute Direct circuits.
2121
### Gateways
2222

23-
FastPath still requires a virtual network gateway to be created to exchange routes between virtual network and on-premises network. For more information about virtual network gateways and ExpressRoute, including performance information, and gateway SKUs, see [ExpressRoute virtual network gateways](expressroute-about-virtual-network-gateways.md).
23+
FastPath still requires a virtual network gateway to be created to exchange routes between a virtual network and an on-premises network. For more information about virtual network gateways and ExpressRoute, including performance information, and gateway SKUs, see [ExpressRoute virtual network gateways](expressroute-about-virtual-network-gateways.md).
2424

2525
To configure FastPath, the virtual network gateway must be either:
2626

@@ -73,7 +73,7 @@ FastPath Private endpoint/Private Link connectivity is supported for the followi
7373
- Third Party Private Link Services
7474

7575
> [!NOTE]
76-
> * Enabling FastPath Private endpoint/Link support for limited GA scenarios may take upwards of 2 weeks to complete. Please plan your deployment(s) in advance.
76+
> * Enabling FastPath Private endpoint/Link support for limited GA scenarios may take upwards of 4 weeks to complete. Please plan your deployment(s) in advance.
7777
> * Connections associated to ExpressRoute partner circuits aren't eligible for this preview. Both IPv4 and IPv6 connectivity is supported.
7878
> * FastPath connectivity to a Private endpoint/Link service deployed to a spoke Virtual Network, peered to the Hub Virtual Network (where the ExpressRoute Virtual Network Gateway is deployed), is not supported. FastPath only supports connectivity to Private Endpoints/Link services deployed to the Hub Virtual Network.
7979
> * Private Link pricing will not apply to traffic sent over ExpressRoute FastPath. For more information about pricing, check out the [Private Link pricing page](https://azure.microsoft.com/pricing/details/private-link/).

articles/reliability/reliability-backup.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ Azure Backup is a secure and reliable built-in data protection mechanism in Azur
2020

2121
Azure Backup supports the following data redundant storage options:
2222

23-
- **Locally redundant storage (LRS):** To protect your data against server rack and drive failures, you can use LRS. LRS replicates your backup data three times within a single data center in the primary region. For more information on locally redundant storage, see [Azure Blog Storage - locally redundant storage](/azure/storage/common/storage-redundancy#locally-redundant-storage).
23+
- **Locally redundant storage (LRS):** To protect your data against server rack and drive failures, you can use LRS. LRS replicates your backup data three times within a single data center in the primary region. For more information on locally redundant storage, see [Azure Blob Storage - locally redundant storage](/azure/storage/common/storage-redundancy#locally-redundant-storage).
2424

25-
- **Geo-redundant storage (GRS):** To protect against region-wide outages, you can use GRS. GRS replicates your backup data to a secondary region. For more information, see [Azure Blog Storage - geo-redundant storage](/azure/storage/common/storage-redundancy#geo-redundant-storage).
25+
- **Geo-redundant storage (GRS):** To protect against region-wide outages, you can use GRS. GRS replicates your backup data to a secondary region. For more information, see [Azure Blob Storage - geo-redundant storage](/azure/storage/common/storage-redundancy#geo-redundant-storage).
2626

27-
- **Zone-redundant storage (ZRS):** To replicate your backup data in availability zones, you can use ZRS. ZRS guarantees data residency and resiliency in the same region. [Azure Blog Storage - zone-redundant storage](/azure/storage/common/storage-redundancy#zone-redundant-storage).
27+
- **Zone-redundant storage (ZRS):** To replicate your backup data in availability zones, you can use ZRS. ZRS guarantees data residency and resiliency in the same region. [Azure Blob Storage - zone-redundant storage](/azure/storage/common/storage-redundancy#zone-redundant-storage).
2828

2929
>[!NOTE]
3030
>The redundancy options are applicable to how backup data is stored and not on the Azure Backup Service itself.

articles/virtual-machines/extensions/key-vault-linux.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Version 3.0+ of the Key Vault VM extension for Linux adds support for the follow
6666
`
6767
## Key Vault VM extension version
6868

69-
* Users can choose to upgrade their existing Key Vault vn extension version to newer version.
69+
* Users can choose to upgrade their existing Key Vault VM extension version to newer version.
7070

7171
* If you prefer to upgrade to newer version, you would need to delete previous version first, then install newer version.
7272
```azurecli

0 commit comments

Comments
 (0)