Skip to content

Commit f67bc34

Browse files
authored
Merge branch 'MicrosoftDocs:main' into chat-composite-public-preview-doc-update
2 parents 77a9f74 + f343d3e commit f67bc34

File tree

5 files changed

+65
-77
lines changed

5 files changed

+65
-77
lines changed

articles/route-server/tutorial-protect-route-server.md

Lines changed: 3 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'Tutorial: Protect your route server with Azure DDoS protection'
2+
title: 'Tutorial: Protect your Route Server with Azure DDoS protection'
33
description: Learn how to set up a route server and protect it with Azure DDoS protection
44
author: asudbring
55
ms.author: allensu
@@ -9,7 +9,7 @@ ms.date: 12/21/2022
99
ms.custom: template-tutorial
1010
---
1111

12-
# Tutorial: Protect your route server with Azure DDoS protection
12+
# Tutorial: Protect your Route Server with Azure DDoS protection
1313

1414
This article helps you create an Azure Route Server with a DDoS protected virtual network. Azure DDoS protection protects your publicly accessible route server from Distributed Denial of Service attacks.
1515

@@ -137,18 +137,6 @@ You'll need the Azure Route Server's peer IPs and ASN to complete the configurat
137137

138138
:::image type="content" source="./media/quickstart-configure-route-server-portal/route-server-overview.png" alt-text="Screenshot of Route Server overview page.":::
139139

140-
## Configure route exchange
141-
142-
1. In the search box at the top of the portal, enter **Route Server**. Select **Route Servers** in the search results.
143-
144-
2. Select **myRouteServer**.
145-
146-
3. In **Settings**, select **Configuration**.
147-
148-
4. Select **Enabled** in **Branch-to-branch**.
149-
150-
5. Select **Save**.
151-
152140
## Clean up resources
153141

154142
If you're not going to continue to use this application, delete the virtual network, DDoS protection plan, and Route Server with the following steps:
@@ -167,5 +155,5 @@ If you're not going to continue to use this application, delete the virtual netw
167155

168156
Advance to the next article to learn how to:
169157
> [!div class="nextstepaction"]
170-
> [Configure peering between Azure Route Server and Quagga network virtual appliance](tutorial-configure-route-server-with-quagga.md)
158+
> [Configure peering between Azure Route Server and network virtual appliance](tutorial-configure-route-server-with-quagga.md)
171159

articles/storage/file-sync/file-sync-storsimple-cost-comparison.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ Azure File Sync has the following pricing components you should consider in the
6060
### Translating quantities from StorSimple
6161
If you are trying to estimate the costs of Azure File Sync based on the expenses you see in StorSimple, be careful with the following items:
6262

63-
- **Azure Files bills on logical size (standard file shares).** Unlike StorSimple, which encodes your data in the StorSimple proprietary format before storing it to Azure Blob storage, Azure Files stores the data from Azure File Sync in the same form as you see it on your Windows File Server. This means that if you are trying to figure out how much storage you will consume in Azure Files, you should look at the logical size of the data from StorSimple, rather than the amount stored in Azure Blob storage. Although this may look like it will cause you to pay more when using Azure File Sync, you need to do the complete analysis including all aspects of StorSimple costs to see the true comparison. Additionally, Azure Files offers capacity reservations that enable you to buy storage at an up-to 36% discount over the list price. See [Capacity reservations in Azure Files](../files/understanding-billing.md#reserve-capacity).
63+
- **Azure Files bills on logical size (standard file shares).** Unlike StorSimple, which encodes your data in the StorSimple proprietary format before storing it to Azure Blob storage, Azure Files stores the data from Azure File Sync in the same form as you see it on your Windows File Server. This means that if you are trying to figure out how much storage you will consume in Azure Files, you should look at the logical size of the data from StorSimple, rather than the amount stored in Azure Blob storage. Although this may look like it will cause you to pay more when using Azure File Sync, you need to do the complete analysis including all aspects of StorSimple costs to see the true comparison. Additionally, Azure Files offers reservations that enable you to buy storage at an up-to 36% discount over the list price. See [Reservations in Azure Files](../files/understanding-billing.md#reservations).
6464

6565
- **Don't assume a 1:1 ratio between transactions on StorSimple and transactions in Azure File Sync.** It might be tempting to look at the number of transactions done by StorSimple in Azure Blob storage and assume that number will be similar to the number of transactions that Azure File Sync will do on Azure Files. This number may overstate or understate the number of transactions Azure File Sync will do, so it's not a good way to estimate transaction costs. The best way to estimate transaction costs is to do a small proof-of-concept in Azure File Sync with a live file share similar to the file shares stored in StorSimple.
6666

0 commit comments

Comments
 (0)