Skip to content

Commit 6ac871e

Browse files
yelevinyelevin
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into yelevin/kusto-updates-2
2 parents d69e0d5 + b9ee3da commit 6ac871e

18 files changed

+113
-627
lines changed

‎articles/azure-netapp-files/azure-netapp-files-resource-limits.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: conceptual
8-
ms.date: 08/09/2024
8+
ms.date: 12/31/2024
99
ms.author: anfdocs
1010
---
1111
# Resource limits for Azure NetApp Files
@@ -31,7 +31,7 @@ The following table describes resource limits for Azure NetApp Files:
3131
| Maximum size of a single regular volume | 100 TiB | No |
3232
| Minimum size of a single [large volume](large-volumes-requirements-considerations.md) | 50 TiB | No |
3333
| Large volume size increase | 30% of lowest provisioned size | Yes |
34-
| Maximum size of a single [large volume](large-volumes-requirements-considerations.md) | 1,024 TiB | No |
34+
| Maximum size of a single [large volume](large-volumes-requirements-considerations.md) | 1,024 TiB | Yes** |
3535
| Maximum size of a single large volume on dedicated capacity (preview) | 2,048 TiB | No |
3636
| Maximum size of a single file | 16 TiB | No |
3737
| Maximum size of directory metadata in a single directory | 320 MB | No |
@@ -52,6 +52,10 @@ The following table describes resource limits for Azure NetApp Files:
5252

5353
\* [!INCLUDE [Limitations for capacity pool minimum of 1 TiB](includes/2-tib-capacity-pool.md)]
5454

55+
56+
57+
\** 2-PiB [large volume](large-volumes-requirements-considerations.md) large volumes are available on request depending on regional dedicated capacity availability. To request 2-PiB large volumes, contact your account team.
58+
5559
For more information, see [Capacity management FAQs](faq-capacity-management.md).
5660

5761
For limits and constraints related to Azure NetApp Files network features, see [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md#considerations).

‎articles/azure-netapp-files/large-volumes-requirements-considerations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: b-ahibbard
66
ms.service: azure-netapp-files
77
ms.custom: references_regions
88
ms.topic: conceptual
9-
ms.date: 10/07/2024
9+
ms.date: 12/31/2024
1010
ms.author: anfdocs
1111
---
1212
# Requirements and considerations for large volumes
@@ -18,7 +18,7 @@ This article describes the requirements and considerations you need to be aware
1818
The following requirements and considerations apply to large volumes. For performance considerations of *regular volumes*, see [Performance considerations for Azure NetApp Files](azure-netapp-files-performance-considerations.md).
1919

2020
* A regular volume can’t be converted to a large volume.
21-
* You must create a large volume at a size of 50 TiB or larger. A single volume can't exceed 1 PiB.
21+
* You must create a large volume at a size of 50 TiB or larger. The maximum size of a large volume is 1,024 TiB, though 2-PiB large volumes are available on request depending on regional dedicated capacity availability. To request 2-PiB large volumes, contact your account team.
2222
* You can't resize a large volume to less than 50 TiB.
2323
A large volume cannot be resized to more than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits).
2424
* Large volumes are currently not supported with Azure NetApp Files backup.

‎articles/load-balancer/load-balancer-troubleshoot-backend-traffic.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Using source persistence distribution mode can cause an uneven distribution of t
2929

3030
Clients that run behind proxies might be seen as one unique client application from the load balancer's point of view.
3131

32-
## VMs behind a load balancer aren't responding to traffic on the configured data port
32+
## Virtual machines behind a load balancer aren't responding to traffic on the configured data port
3333

3434
If a backend pool VM is listed as healthy and responds to the health probes, but is still not participating in the load balancing, or isn't responding to the data traffic, it may be due to any of the following reasons:
3535

@@ -109,6 +109,11 @@ The symptom for this scenario is intermittent connection timeouts when the flow
109109
110110
You can combine an internal load balancer with any third-party proxy or use internal [Application Gateway](../application-gateway/overview.md) for proxy scenarios with HTTP/HTTPS. While you could use a public load balancer to mitigate this issue, the resulting scenario is prone to [SNAT exhaustion](load-balancer-outbound-connections.md). Avoid this second approach unless carefully managed.
111111
112+
## Virtual machines removed from a load balancer are receiving traffic
113+
114+
It is by design that existing TCP connections will continue to a virtual machine even after a backend is removed from a load balancer. Once a connection is routed to a backend instance by the load balancer, traffic is established directly between the client and the backend instance. Connections will continue untl the virtual machine is stopped or deallocated.
115+
116+
112117
## Next steps
113118
114119
If the preceding steps don't resolve the issue, open a [support ticket](https://azure.microsoft.com/support/options/).

‎articles/network-watcher/traffic-analytics.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: azure-network-watcher
88
ms.topic: concept-article
9-
ms.date: 12/29/2024
9+
ms.date: 12/31/2024
1010
ms.custom: references_regions
1111

1212
#CustomerIntent: As an Azure administrator, I want to use Traffic analytics to analyze Network Watcher flow logs so that I can view network activity, secure my networks, and optimize performance.
@@ -93,13 +93,11 @@ To use traffic analytics, you need the following components:
9393
> | ---------------- | ---- |
9494
> | Resource Manager | [Owner](../role-based-access-control/built-in-roles.md?toc=/azure/network-watcher/toc.json#owner) |
9595
> | | [Contributor](../role-based-access-control/built-in-roles.md?toc=/azure/network-watcher/toc.json#contributor) |
96-
> | | [Network contributor](../role-based-access-control/built-in-roles.md?toc=/azure/network-watcher/toc.json#network-contributor) <sup>1</sup> and [Monitoring contributor](../role-based-access-control/built-in-roles.md?toc=/azure/network-watcher/toc.json#monitoring-contributor) <sup>2</sup> |
96+
> | | [Network contributor](../role-based-access-control/built-in-roles.md?toc=/azure/network-watcher/toc.json#network-contributor) <sup>1</sup> and [Monitoring contributor](../role-based-access-control/built-in-roles.md?toc=/azure/network-watcher/toc.json#monitoring-contributor) |
9797
>
9898
> <sup>1</sup> Network contributor doesn't cover `Microsoft.OperationalInsights/workspaces/*` actions.
9999
>
100-
> <sup>2</sup> Only required when using traffic analytics to analyze virtual network flow logs.
101-
>
102-
> If none of the preceding built-in roles are assigned to your account, assign a [custom role](../role-based-access-control/custom-roles.md?toc=/azure/network-watcher/toc.json) that supports the actions listed in [Traffic analytics permissions](required-rbac-permissions.md#traffic-analytics).
100+
> If none of the preceding built-in roles are assigned to your account, assign a [custom role](../role-based-access-control/custom-roles.md?toc=/azure/network-watcher/toc.json) that supports the actions listed in [Flow logs](required-rbac-permissions.md#flow-logs) and [Traffic analytics](required-rbac-permissions.md#traffic-analytics) permissions.
103101
104102
## How traffic analytics works
105103

@@ -115,7 +113,7 @@ Reduced logs are enhanced with geography, security, and topology information and
115113

116114
The following tables list the supported regions where you can enable traffic analytics for your flow logs and the Log Analytics workspaces that you can use.
117115

118-
#### [North America / South America](#tab/Americas)
116+
# [North America / South America](#tab/Americas)
119117

120118
> [!div class="mx-tableFixed"]
121119
> | Region | Network security group flow logs | Virtual network flow logs | Traffic analytics | Log Analytics workspace |
@@ -135,7 +133,7 @@ The following tables list the supported regions where you can enable traffic ana
135133
> | West US 2 | ✓ | ✓ | ✓ | ✓ |
136134
> | West US 3 | ✓ | ✓ | ✓ | ✓ |
137135
138-
#### [Europe](#tab/Europe)
136+
# [Europe](#tab/Europe)
139137

140138
> [!div class="mx-tableFixed"]
141139
> | Region | Network security group flow logs | Virtual network flow logs | Traffic analytics | Log Analytics workspace |
@@ -157,7 +155,7 @@ The following tables list the supported regions where you can enable traffic ana
157155
> | UK West | ✓ | ✓ | ✓ | ✓ |
158156
> | West Europe | ✓ | ✓ | ✓ | ✓ |
159157
160-
#### [Australia / Asia / Pacific](#tab/APAC)
158+
# [Australia / Asia / Pacific](#tab/APAC)
161159

162160
> [!div class="mx-tableFixed"]
163161
> | Region | Network security group flow logs | Virtual network flow logs | Traffic analytics | Log Analytics workspace |
@@ -186,7 +184,7 @@ The following tables list the supported regions where you can enable traffic ana
186184
> | Taiwan Northwest | ✓ | ✓ | | |
187185
> | West India | ✓ | ✓ | | |
188186
189-
#### [Middle East / Africa](#tab/MiddleEast)
187+
# [Middle East / Africa](#tab/MiddleEast)
190188

191189
> [!div class="mx-tableFixed"]
192190
> | Region | Network security group flow logs | Virtual network flow logs | Traffic analytics | Log Analytics workspace |
@@ -198,7 +196,7 @@ The following tables list the supported regions where you can enable traffic ana
198196
> | UAE Central | ✓ | ✓ | ✓ | ✓ |
199197
> | UAE North | ✓ | ✓ | ✓ | ✓ |
200198
201-
#### [Azure Government](#tab/AzGov)
199+
# [Azure Government](#tab/AzGov)
202200

203201
> [!div class="mx-tableFixed"]
204202
> | Region | Network security group flow logs | Virtual network flow logs | Traffic analytics | Log Analytics workspace |

‎articles/oracle/oracle-db/oracle-database-regions.md

Lines changed: 25 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -12,50 +12,45 @@ ms.author: jacobjaygbay
1212

1313
# Region availability for Oracle Database@Azure
1414

15-
Learn what Azure regions and corresponding Oracle Cloud Infrastructure (OCI) regions support Oracle Database@Azure in standard business regions across the globe.
15+
Learn what Azure regions and corresponding Oracle Cloud Infrastructure (OCI) regions support Oracle Database@Azure in standard business regions across the globe.
16+
17+
The list below mentions the Azure and corresponding OCI regions with the regional availability for Oracle Database@Azure:
18+
- Dual – Minimum two Azure zones are available in this region
19+
- Single – One Azure zone available with a corresponding paired DR region
20+
- DR - Disaster recovery only region
1621

1722
## Asia Pacific (APAC)
1823

19-
The following table lists Azure regions and corresponding OCI regions that support Oracle Database@Azure in the APAC business region:
24+
| Azure region | OCI region | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure | Regional Availability |
25+
| -------------- | ----------------------- | ----------------------------- | -------------------------------- | ---------|
26+
| Australia East | Australia East (Sydney) | ✓ | ✓ | Single |
2027

21-
| Azure region | OCI region | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure |
22-
|----------------|--------------------------|-------------------|-------------------|
23-
| Australia East | Australia East (Sydney) | ✓ | ✓ |
2428

2529
## Brazil
2630

27-
| Azure region | OCI region | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure |
28-
|----------------|--------------------------|-------------------|-------------------|
29-
| Brazil South | Brazil Southeast (Vinhedo) | ✓ | ✓ |
31+
| Azure region | OCI region | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure | Regional Availability |
32+
|----------------|--------------------------|-------------------|-------------------|----|
33+
| Brazil South | Brazil Southeast (Vinhedo) | ✓ | ✓ | Dual |
34+
3035

3136
## Europe, Middle East, Africa (EMEA)
3237

33-
The following table lists Azure regions and corresponding OCI regions that support Oracle Database@Azure in the EMEA business region:
38+
|Azure region |OCI region | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure | Regional Availability |
39+
|------------|--|--------------------------|------------------------------| ---- |
40+
| France Central |France central (Paris) | ✓ | ✓ | Dual |
41+
| Germany West Central |Germany Central (Frankfurt) | ✓ | ✓ | DR |
42+
| UK South | UK South (London) | ✓ | ✓ | Single|
43+
| Italy North | Italy North (Milan) | ✓ | | Dual |
44+
| UK West | UK West (Cardiff) | ✓ | ✓ | Single |
3445

35-
|Azure region |OCI region | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure |
36-
|------------|--|--------------------------|------------------------------|
37-
| France Central |France central (Paris) | ✓ | ✓ |
38-
| Germany West Central |Germany Central (Frankfurt) | ✓ | ✓ |
39-
| UK South | UK South (London) | ✓ | ✓ |
40-
| Italy North | Italy North (Milan) | ✓ | |
4146

4247
## North America (NA)
4348

44-
The following table lists Azure regions and corresponding OCI regions that support Oracle Database@Azure in the NA business region:
45-
46-
| Azure region | OCI region | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure |
47-
| -------------- | -------------------|------------------------|------------------ |
48-
| East US | US East (Ashburn) | ✓ | ✓ |
49-
| Canada Central | Canada Southeast (Toronto) | ✓ | ✓ |
50-
51-
## Disaster recovery regions available for Oracle Database@Azure
52-
53-
The following table lists Azure regions and corresponding OCI regions that offer a single-zone disaster recovery solution for Oracle Database@Azure:
54-
55-
| Azure region | OCI region | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure |
56-
|----------------|--------------------------|-------------------|-------------------|
57-
| West US | US West (San Jose) | ✓ | ✓ |
58-
| UK West | UK West (Cardiff) | ✓ | ✓ |
49+
| Azure region | OCI region | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure | Regional Availability|
50+
| -------------- | -------------------|------------------------|------------------ | -----|
51+
| East US | US East (Ashburn) | ✓ | ✓ | Dual |
52+
| Canada Central | Canada Southeast (Toronto) | ✓ | ✓ | Single |
53+
| West US | US West (San Jose) | ✓ | ✓ | Single |
5954

6055
> [!NOTE]
6156
> To provision Oracle Database@Azure resources in a supported region, your tenancy must be subscribed to the target region. Learn how to [manage regions](https://docs.oracle.com/iaas/Content/Identity/regions/managingregions.htm#Managing_Regions) and [subscribe to an infrastructure region](https://docs.oracle.com/iaas/Content/Identity/regions/To_subscribe_to_an_infrastructure_region.htm#subscribe).

‎articles/sap/workloads/sap-hana-high-availability.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ Replace `<placeholders>` with the values for your SAP HANA installation.
144144
1. Run this command to list all the available disks:
145145

146146
```bash
147-
/dev/disk/azure/scsi1/lun*
147+
ls /dev/disk/azure/scsi1/lun*
148148
```
149149

150150
Example output:

‎articles/synapse-analytics/.openpublishing.redirection.synapse-analytics.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,16 @@
2525
"redirect_url": "/azure/synapse-analytics/partner/data-integration",
2626
"redirect_document_id": false
2727
},
28+
{
29+
"source_path_from_root": "/articles/synapse-analytics/machine-learning/tutorial-automl.md",
30+
"redirect_url": "/azure/synapse-analytics/machine-learning/what-is-machine-learning",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path_from_root": "/articles/synapse-analytics/spark/apache-spark-azure-machine-learning-tutorial.md",
35+
"redirect_url": "/azure/synapse-analytics/machine-learning/what-is-machine-learning",
36+
"redirect_document_id": false
37+
},
2838
{
2939
"source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-partner-data-management.md",
3040
"redirect_url": "/azure/synapse-analytics/partner/data-management",

‎articles/synapse-analytics/database-designer/quick-start-create-lake-database.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: wiassaf, jovanpop
77
ms.service: azure-synapse-analytics
88
ms.subservice: database-editor
99
ms.topic: quickstart
10-
ms.date: 08/16/2022
10+
ms.date: 12/31/2024
1111
ms.custom: template-concept
1212
---
1313

@@ -23,9 +23,9 @@ This quick start gives you a complete sample scenario on how you can apply datab
2323

2424
## Create a lake database from database templates
2525

26-
Use the new database templates functionality to create a lake database that you can use to configure your data model for the database.
26+
Use the new database templates functionality to create a lake database that you can use to configure your data model for the database.
2727

28-
For our scenario we will use the `Retail` database template and select the following entities:
28+
For our scenario we'll use the `Retail` database template and select the following entities:
2929

3030
- **RetailProduct** - A product is anything that can be offered to a market that might satisfy a need by potential customers. That product is the sum of all physical, psychological, symbolic, and service attributes associated with it.
3131
- **Transaction** - The lowest level of executable work or customer activity.
@@ -43,7 +43,7 @@ The easiest way to find entities is by using the search box above the different
4343

4444
After you have created the database, make sure the storage account and the filepath is set to a location where you wish to store the data. The path will default to the primary storage account within Azure Synapse Analytics but can be changed to your needs.
4545

46-
:::image type="content" source="./media/quick-start-create-lake-database/lake-database-example.png" alt-text="Screenshot of an individual entity properties in the Retail database template." lightbox="./media/quick-start-create-lake-database/lake-database-example.png":::
46+
:::image type="content" source="./media/quick-start-create-lake-database/lake-database-example.png" alt-text="Screenshot of an individual entity property in the Retail database template." lightbox="./media/quick-start-create-lake-database/lake-database-example.png":::
4747

4848
To save your layout and make it available within Azure Synapse, **Publish** all changes. This step completes the setup of the lake database and makes it available to all components within Azure Synapse Analytics and outside.
4949

@@ -77,10 +77,6 @@ df = spark.sql("SELECT * FROM `Retail_mil`.`RetailProduct`")
7777
df.show(10)
7878
```
7979

80-
## Train machine learning models
81-
82-
You can use lake database to train your machine learning models and score the data. For more details [Train machine learning models](../machine-learning/tutorial-automl.md)
83-
8480
## Next steps
8581

8682
Continue to explore the capabilities of the database designer using the links below.

0 commit comments

Comments
 (0)