Skip to content

Commit 1b92809

Browse files
Learn Build Service GitHub AppLearn Build Service GitHub App
authored andcommitted
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents 9ed39fd + 53a796c commit 1b92809

File tree

91 files changed

+1299
-161
lines changed

Some content is hidden

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

91 files changed

+1299
-161
lines changed

articles/azure-cache-for-redis/cache-remove-tls-10-11.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ To meet the industry-wide push toward the exclusive use of Transport Layer Secur
1818
TLS versions 1.0 and 1.1 also don't support the modern encryption methods and cipher suites recommended by Payment Card Industry (PCI) compliance standards. This [TLS security blog](https://www.acunetix.com/blog/articles/tls-vulnerabilities-attacks-final-part/) explains some of these vulnerabilities in more detail.
1919

2020
> [!IMPORTANT]
21-
> On November 1, 2024, the TLS 1.2 requirement will be enforced.
21+
> Starting November 1, 2024, the TLS 1.2 requirement will be enforced.
2222
>
2323
>
2424
@@ -36,7 +36,7 @@ As a part of this effort, you can expect the following changes to Azure Cache fo
3636
| September 2023 | TLS 1.0/1.1 retirement announcement |
3737
| March 1, 2024 | Beginning March 1, 2024, you can't create new caches with the Minimum TLS version set to 1.0 or 1.1 and you can't set the _MinimumTLSVersion_ to 1.0 or 1.1 for your existing cache. The minimum TLS version won't be updated automatically for existing caches at this point. |
3838
| October 31, 2024 | Ensure that all your applications are connecting to Azure Cache for Redis using TLS 1.2 and Minimum TLS version on your cache settings is set to 1.2. |
39-
| November 1, 2024 | Minimum TLS version for all cache instances is updated to 1.2. This means Azure Cache for Redis instances reject connections using TLS 1.0 or 1.1 at this point. |
39+
| Starting November 1, 2024 | Minimum TLS version for all cache instances is updated to 1.2. This means Azure Cache for Redis instances reject connections using TLS 1.0 or 1.1 at this point. |
4040

4141
> [!IMPORTANT]
4242
> The content in this article does not apply to Azure Cache for Redis Enterprise/Enterprise Flash because the Enterprise tiers only support TLS 1.2.

articles/azure-maps/creator-onboarding-tool.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ Integrate the indoor map into your applications using the Web SDK.
7979
> [!div class="nextstepaction"]
8080
> [Use the Azure Maps Indoor Maps module]
8181
82-
[Azure Maps Creator onboarding tool]: creator-onboarding-tool.md
82+
[Azure Maps Creator onboarding tool]: https://azure.github.io/azure-maps-creator-onboarding-tool
8383
[Conversion service]: /rest/api/maps-creator/conversion
8484
[Convert a drawing package]: creator-indoor-maps.md#convert-a-drawing-package
8585
[dataset]: creator-indoor-maps.md#datasets

articles/azure-netapp-files/azure-netapp-files-register.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,14 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 01/21/2022
8+
ms.date: 10/15/2024
99
ms.author: anfdocs
1010
---
1111
# Register for NetApp Resource Provider
1212

13-
To use the Azure NetApp Files service, you need to register the NetApp Resource Provider.
13+
To use Azure NetApp Files, you need to register the NetApp Resource Provider.
1414

15-
1. From the Azure portal, click the Azure Cloud Shell icon on the upper right-hand corner:
15+
1. From the Azure portal, select the Azure Cloud Shell icon on the upper right-hand corner:
1616

1717
![Azure Cloud Shell icon](./media/azure-netapp-files-register/azure-netapp-files-azure-cloud-shell.png)
1818

@@ -30,7 +30,7 @@ To use the Azure NetApp Files service, you need to register the NetApp Resource
3030
3131
The `--wait` parameter instructs the console to wait for the registration to complete. The registration process can take some time to complete.
3232
33-
4. In the Azure Cloud Shell console, enter the following command to verify that the Azure Resource Provider has been registered:
33+
4. Verify that the Azure Resource Provider has been registered. To verify, enter the following command in the Azure Cloud Shell console:
3434
3535
```azurecli
3636
az provider show --namespace Microsoft.NetApp
@@ -46,11 +46,11 @@ To use the Azure NetApp Files service, you need to register the NetApp Resource
4646
"resourceTypes": [….
4747
```
4848
49-
`<SubID>` is your subscription ID. The `state` parameter value indicates `Registered`.
49+
`<SubID>` is your subscription ID. The `state` parameter value indicates `Registered`.
5050
51-
5. From the Azure portal, click the **Subscriptions** blade.
52-
6. In the Subscriptions blade, click your subscription ID.
53-
7. In the settings of the subscription, click **Resource providers** to verify that Microsoft.NetApp Provider indicates the Registered status:
51+
5. From the Azure portal, select **Subscriptions**.
52+
6. From Subscriptions, select your subscription ID.
53+
7. In the settings of the subscription, select **Resource providers** to verify that Microsoft.NetApp Provider indicates the Registered status:
5454
5555
![Registered Microsoft.NetApp](./media/azure-netapp-files-register/azure-netapp-files-registered-resource-providers.png)
5656

articles/azure-netapp-files/faq-data-migration-protection.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.service: azure-netapp-files
55
ms.topic: conceptual
66
author: b-hchen
77
ms.author: anfdocs
8-
ms.date: 08/31/2023
8+
ms.date: 10/15/2024
99
---
1010
# Data migration and protection FAQs for Azure NetApp Files
1111

@@ -14,7 +14,7 @@ This article answers frequently asked questions (FAQs) about Azure NetApp Files
1414
## How do I migrate data to Azure NetApp Files?
1515
Azure NetApp Files provides NFS and SMB volumes. You can use any file-based copy tool to migrate data to the service.
1616

17-
For more information about the Azure File Migration Program, see [Migrate the critical file data you need to power your applications](https://techcommunity.microsoft.com/t5/azure-storage-blog/migrate-the-critical-file-data-you-need-to-power-your/ba-p/3038751). Also, see [Azure Storage migration tools comparison - Unstructured data](../storage/solution-integration/validated-partners/data-management/migration-tools-comparison.md).
17+
For more information about the Azure File Migration Program, see [Migrate the critical file data you need to power your applications](https://techcommunity.microsoft.com/t5/azure-storage-blog/migrate-the-critical-file-data-you-need-to-power-your/ba-p/3038751). Also, see [Azure Storage migration tools comparison - Unstructured data](../storage/solution-integration/validated-partners/data-management/migration-tools-comparison.md).
1818

1919
NetApp offers a SaaS-based solution, [NetApp Cloud Sync](https://cloud.netapp.com/cloud-sync-service). The solution enables you to replicate NFS or SMB data to Azure NetApp Files NFS exports or SMB shares.
2020

@@ -25,7 +25,7 @@ Migration of certain structured datasets (such as databases) is best done using
2525
The requirements for data migration from on premises to Azure NetApp Files are as follows:
2626

2727
- Ensure Azure NetApp Files is available in the target Azure region.
28-
- Validate network connectivity between the source and the Azure NetApp Files target volume IP address. Data transfer between on premises and the Azure NetApp Files service is supported over ExpressRoute.
28+
- Validate network connectivity between the source and the Azure NetApp Files target volume IP address. Data transfer between on premises and the Azure NetApp Files service is supported over ExpressRoute. The virtual machine running that the data transfer tool runs on should have access to both the source and destination volumes.
2929
- Create the target Azure NetApp Files volume.
3030
- Transfer the source data to the target volume by using your preferred file copy tool.
3131

@@ -38,13 +38,13 @@ By default, your data stays within the region where you deploy your Azure NetApp
3838

3939
## How do I create a copy of an Azure NetApp Files volume in another Azure region?
4040

41-
Azure NetApp Files provides NFS and SMB volumes. Any file based-copy tool can be used to replicate data between Azure regions.
41+
Azure NetApp Files provides NFS and SMB volumes. Any file based-copy tool can be used to replicate data between Azure regions.
4242

43-
The [cross-region replication](cross-region-replication-introduction.md) functionality enables you to asynchronously replicate data from an Azure NetApp Files volume (source) in one region to another Azure NetApp Files volume (destination) in another region. Additionally, you can [create a new volume by using a snapshot of an existing volume](snapshots-restore-new-volume.md).
43+
The [cross-region replication](cross-region-replication-introduction.md) functionality enables you to asynchronously replicate data from an Azure NetApp Files volume (source) in one region to another Azure NetApp Files volume (destination) in another region. Additionally, you can [create a new volume by using a snapshot of an existing volume](snapshots-restore-new-volume.md).
4444

45-
NetApp offers a SaaS based solution, [NetApp Cloud Sync](https://cloud.netapp.com/cloud-sync-service). The solution enables you to replicate NFS or SMB data to Azure NetApp Files NFS exports or SMB shares.
45+
NetApp offers a SaaS based solution, [NetApp Cloud Sync](https://cloud.netapp.com/cloud-sync-service). The solution enables you to replicate NFS or SMB data to Azure NetApp Files NFS exports or SMB shares.
4646

47-
You can also use a wide array of free tools to copy data. For NFS, you can use workloads tools such as [rsync](https://rsync.samba.org/examples.html) to copy and synchronize source data into an Azure NetApp Files volume. For SMB, you can use workloads [robocopy](/windows-server/administration/windows-commands/robocopy) in the same manner. These tools can also replicate file or folder permissions.
47+
You can also use a wide array of free tools to copy data. For NFS, you can use workloads tools such as [rsync](https://rsync.samba.org/examples.html) to copy and synchronize source data into an Azure NetApp Files volume. For SMB, you can use workloads [robocopy](/windows-server/administration/windows-commands/robocopy) in the same manner. These tools can also replicate file or folder permissions.
4848

4949
The requirements for replicating an Azure NetApp Files volume to another Azure region are as follows:
5050
- Ensure Azure NetApp Files is available in the target Azure region.

articles/communication-services/resources/troubleshooting/voice-video-calling/includes/codes/call-end.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: sloanster
66

77
ms.service: azure-communication-services
88
ms.subservice: azure-communication-services
9-
ms.date: 10/10/2024
9+
ms.date: 10/15/2024
1010
ms.topic: include
1111
ms.custom: include file
1212
ms.author: micahvivion
@@ -44,7 +44,7 @@ There are different explanations for why a call ended. Here are the meanings of
4444
| 3100 | 410 | Call setup failed due to unexpected network problem on the client, check the client's network and retry. | UnxpectedClientError | Check network configuration, make sure it follows Azure Communication Calling network [requirements](../../../../../concepts/voice-video-calling/network-requirements.md). |
4545
| 3101 | 410 | Call dropped due to unexpected network problem on the client, check the client's network and retry. | UnxpectedClientError | Check network configuration, make sure it follows Azure Communication Calling network [requirements](../../../../../concepts/voice-video-calling/network-requirements.md). |
4646
| 3111 | 410 | Call setup failed, unable to process media offer while connecting the call. | UnxpectedClientError | Try again. If issue persists, gather [call info](../../references/how-to-collect-call-info.md), [client logs](../../references/how-to-collect-client-logs.md), [browser console logs](../../references/how-to-collect-browser-verbose-log.md) and contact Azure Communication Services support. |
47-
| 3112 | 410 | Call setup failed due to network configuration problem on the client side, check the client's network configuration, and retry. | ExpectedError | |
47+
| 3112 | 410 | Call setup failed due to network configuration problem on the client side, check the client's network configuration, and retry. | ExpectedError | Learn more details about a call ending with a subcode of 3112 [here](../../../../troubleshooting/voice-video-calling/call-setup-issues/call-ends-with-410-3112.md). |
4848
| 4097 | 0 | Call ended for all users by the meeting organizer. | Success | |
4949
| 4502 | 490 | Call failed due to network connectivity problems, browser failed to complete the network HTTP request. | UnexpectedClientError | Client failed to complete HTTP request and response. Try again. If issue persists, gather [call info](../../references/how-to-collect-call-info.md), [client logs](../../references/how-to-collect-client-logs.md), [browser console logs](../../references/how-to-collect-browser-verbose-log.md) and contact Azure Communication Services support. |
5050
| 4506 | 408 | Call timed out. Check if the callee received and accepted the call. | UnexpectedClientError | Try again. If issue persists, gather [call info](../../references/how-to-collect-call-info.md), [client logs](../../references/how-to-collect-client-logs.md), [browser console logs](../../references/how-to-collect-browser-verbose-log.md) and contact Azure Communication Services support. |

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ The following items are currently unsupported by cost allocation:
130130
- [Cost Management Power BI App](https://appsource.microsoft.com/product/power-bi/costmanagement.azurecostmanagementapp)
131131
- [Power BI Desktop connector](/power-bi/connect-data/desktop-connect-azure-cost-management)
132132

133-
The [Usage Details](/rest/api/consumption/usagedetails/list) API version `2021-10-01` and later supports cost allocation data.
133+
The [Cost Details](/rest/api/cost-management/generate-cost-details-report/create-operation?view=rest-cost-management-2023-11-01&tabs=HTTP) API and [Exports](/rest/api/cost-management/exports/create-or-update?view=rest-cost-management-2023-11-01&tabs=HTTP) support cost allocation data. However, the [Usage Details](/rest/api/consumption/usagedetails/list) API doesn't support cost allocation data.
134134

135135
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.
136136

articles/cost-management-billing/manage/pay-by-invoice.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.reviewer: lishepar
66
ms.service: cost-management-billing
77
ms.subservice: billing
88
ms.topic: how-to
9-
ms.date: 08/06/2024
9+
ms.date: 10/15/2024
1010
ms.author: banders
1111
---
1212

@@ -40,10 +40,7 @@ To qualify for wire transfer payments, you must:
4040
- Have a subscription cost that exceeds a certain amount. This amount varies by service location.
4141

4242
> [!IMPORTANT]
43-
> - Payment by wire transfer is available only for customers who use Azure on behalf of a company.
4443
> - You must pay all outstanding charges before switching to payment by wire transfer.
45-
> - Your default payment method pays any outstanding invoice. To have a wire transfer pay an outstanding invoice, you must change your default payment method to wire transfer after you're approved.
46-
> - Currently, payment by wire transfer isn't supported for Azure global in China.
4744
> - If you switch to payment by wire transfer, you can't switch back to paying by credit or debit card, except for one-time payments.
4845
> - As of September 30, 2023, Microsoft no longer accepts checks as a payment method.
4946

articles/cost-management-billing/reservations/azure-openai.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ For example, assume that your total consumption of provisioned throughput units
5151
5252
## Buy a Microsoft Azure OpenAI reservation
5353

54-
When you by a reservation, the current UTC date and time are used to record the transaction.
54+
When you buy a reservation, the current UTC date and time are used to record the transaction.
5555

5656
To buy an Azure OpenAI reservation, follow these steps:
5757

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Resources that run in a subscription with other offer types don't receive the re
7070

7171
## Purchase reservations
7272

73-
When you by a reservation, the current UTC date and time are used to record the transaction.
73+
When you buy a reservation, the current UTC date and time are used to record the transaction.
7474

7575
You can purchase reservations from Azure portal, APIs, PowerShell, CLI. Read the following articles that apply to you when you're ready to make a reservation purchase:
7676

0 commit comments

Comments
 (0)