Skip to content

Commit cb3ff16

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ip-peering-direct
2 parents 8c1044b + 4fd7c13 commit cb3ff16

File tree

6 files changed

+39
-43
lines changed

6 files changed

+39
-43
lines changed

articles/container-apps/quickstart-code-to-cloud.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ If the `up` command doesn't find a Dockerfile, it automatically uses Buildpacks
178178
::: zone-end
179179

180180

181-
In the following code example, the `.` (dot) tells `containerapp up` to run in the `src` directory of the extracted sample API application.
181+
In the following code example, the `.` (dot) tells `containerapp up` to run in the current directory of the extracted sample API application.
182182

183183
# [Bash](#tab/bash)
184184

articles/network-watcher/network-watcher-visualize-nsg-flow-logs-open-source-tools.md

Lines changed: 3 additions & 9 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: how-to
9-
ms.date: 09/26/2024
9+
ms.date: 10/23/2024
1010
---
1111

1212
# Visualize Azure Network Watcher NSG flow logs using open source tools
@@ -235,19 +235,15 @@ The sample dashboard provides several visualizations of the flow logs:
235235
236236
5. Top 10 Source/Destination IPs – bar charts showing the top 10 source and destination IPs. You can adjust these charts to show more or less top IPs. From here, you can see the most commonly occurring IPs and the traffic decision (allow or deny) being made towards each IP.
237237
238-
![Screenshot shows a sample dashboard with flows by top ten source and destination I P addresses.][6]
239-
240-
6. Flow Tuples – this table shows you the information contained within each flow tuple, and its corresponding NGS and rule.
241-
242-
![Screenshot shows flow tuples in a table.][7]
238+
6. Flow Tuples – a table showing the information contained within each flow tuple, and its corresponding NGS and rule.
243239
244240
Using the query bar at the top of the dashboard, you can filter down the dashboard based on any parameter of the flows, such as subscription ID, resource groups, rule, or any other variable of interest. For more about Kibana's queries and filters, see the [official documentation](https://www.elastic.co/guide/en/beats/packetbeat/current/kibana-queries-filters.html)
245241
246242
## Conclusion
247243
248244
By combining the network security group flow logs with the Elastic Stack, we have come up with powerful and customizable way to visualize our network traffic. These dashboards allow you to quickly gain and share insights about your network traffic, and filter down and investigate on any potential anomalies. Using Kibana, you can tailor these dashboards and create specific visualizations to meet any security, audit, and compliance needs.
249245
250-
## Next steps
246+
## Next step
251247
252248
Learn how to visualize your NSG flow logs with Power BI by visiting [Visualize NSG flows logs with Power BI](network-watcher-visualize-nsg-flow-logs-power-bi.md)
253249
@@ -259,5 +255,3 @@ Learn how to visualize your NSG flow logs with Power BI by visiting [Visualize N
259255
[3]: ./media/network-watcher-visualize-nsg-flow-logs-open-source-tools/figure3.png
260256
[4]: ./media/network-watcher-visualize-nsg-flow-logs-open-source-tools/figure4.png
261257
[5]: ./media/network-watcher-visualize-nsg-flow-logs-open-source-tools/figure5.png
262-
[6]: ./media/network-watcher-visualize-nsg-flow-logs-open-source-tools/figure6.png
263-
[7]: ./media/network-watcher-visualize-nsg-flow-logs-open-source-tools/figure7.png

articles/storage/files/files-smb-protocol.md

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about file shares hosted in Azure Files using the Server Mess
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: conceptual
7-
ms.date: 07/08/2024
7+
ms.date: 10/23/2024
88
ms.author: kendownie
99
ms.custom: devx-track-azurepowershell
1010
---
@@ -154,6 +154,34 @@ az storage account file-service-properties update \
154154
```
155155
---
156156

157+
### Enable SMB Multichannel on older operating systems
158+
159+
Support for SMB Multichannel in Azure Files requires ensuring Windows has all the relevant patches applied. Several older Windows versions, including Windows Server 2016, Windows 10 version 1607, and Windows 10 version 1507, require additional registry keys to be set for all relevant SMB Multichannel fixes to be applied on fully patched installations. If you're running a version of Windows that's newer than these three versions, no additional action is required.
160+
161+
#### Windows Server 2016 and Windows 10 version 1607
162+
163+
To enable all SMB Multichannel fixes for Windows Server 2016 and Windows 10 version 1607, run the following PowerShell command:
164+
165+
```PowerShell
166+
Set-ItemProperty `
167+
-Path "HKLM:SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" `
168+
-Name "2291605642" `
169+
-Value 1 `
170+
-Force
171+
```
172+
173+
#### Windows 10 version 1507
174+
175+
To enable all SMB Multichannel fixes for Windows 10 version 1507, run the following PowerShell command:
176+
177+
```PowerShell
178+
Set-ItemProperty `
179+
-Path "HKLM:\SYSTEM\CurrentControlSet\Services\MRxSmb\KBSwitch" `
180+
-Name "{FFC376AE-A5D2-47DC-A36F-FE9A46D53D75}" `
181+
-Value 1 `
182+
-Force
183+
```
184+
157185
### SMB security settings
158186

159187
Azure Files exposes settings that let you toggle the SMB protocol to be more compatible or more secure, depending on your organization's requirements. By default, Azure Files is configured to be maximally compatible, so keep in mind that restricting these settings may cause some clients not to be able to connect.

articles/storage/files/storage-how-to-use-files-windows.md

Lines changed: 6 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn to use Azure file shares with Windows and Windows Server. Use
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: how-to
7-
ms.date: 05/13/2024
7+
ms.date: 10/23/2024
88
ms.author: kendownie
99
ms.custom: ai-video-demo
1010
ai-usage: ai-assisted
@@ -29,6 +29,8 @@ The steps in the video are also described in the following sections.
2929

3030
In order to use an Azure file share via the public endpoint outside of the Azure region it's hosted in, such as on-premises or in a different Azure region, the OS must support SMB 3.x. Older versions of Windows that support only SMB 2.1 can't mount Azure file shares via the public endpoint.
3131

32+
Azure Files supports [SMB Multichannel](files-smb-protocol.md#smb-multichannel) on premium file shares only.
33+
3234
| Windows version | SMB version | Azure Files SMB Multichannel | Maximum SMB channel encryption |
3335
|-|-|-|-|
3436
| Windows 11, version 22H2 | SMB 3.1.1 | Yes | AES-256-GCM |
@@ -43,9 +45,9 @@ In order to use an Azure file share via the public endpoint outside of the Azure
4345
| Windows 10, version 2004 | SMB 3.1.1 | Yes, with KB5003690 or newer | AES-128-GCM |
4446
| Windows Server 2019 | SMB 3.1.1 | Yes, with KB5003703 or newer | AES-128-GCM |
4547
| Windows 10, version 1809 | SMB 3.1.1 | Yes, with KB5003703 or newer | AES-128-GCM |
46-
| Windows Server 2016 | SMB 3.1.1 | Yes, with KB5004238 or newer and [applied registry key](#windows-server-2016-and-windows-10-version-1607) | AES-128-GCM |
47-
| Windows 10, version 1607 | SMB 3.1.1 | Yes, with KB5004238 or newer and [applied registry key](#windows-server-2016-and-windows-10-version-1607) | AES-128-GCM |
48-
| Windows 10, version 1507 | SMB 3.1.1 | Yes, with KB5004249 or newer and [applied registry key](#windows-10-version-1507) | AES-128-GCM |
48+
| Windows Server 2016 | SMB 3.1.1 | Yes, with KB5004238 or newer and [applied registry key](files-smb-protocol.md#windows-server-2016-and-windows-10-version-1607) | AES-128-GCM |
49+
| Windows 10, version 1607 | SMB 3.1.1 | Yes, with KB5004238 or newer and [applied registry key](files-smb-protocol.md#windows-server-2016-and-windows-10-version-1607) | AES-128-GCM |
50+
| Windows 10, version 1507 | SMB 3.1.1 | Yes, with KB5004249 or newer and [applied registry key](files-smb-protocol.md#windows-10-version-1507) | AES-128-GCM |
4951
| Windows Server 2012 R2 | SMB 3.0 | No | AES-128-CCM |
5052
| Windows 8.1 | SMB 3.0 | No | AES-128-CCM |
5153
| Windows Server 2012 | SMB 3.0 | No | AES-128-CCM |
@@ -134,34 +136,6 @@ For Azure Government Cloud, change the servername to:
134136

135137
`\\storageaccountname.file.core.usgovcloudapi.net\myfileshare`
136138

137-
## Enable SMB Multichannel
138-
139-
Support for SMB Multichannel in Azure Files requires ensuring Windows has all the relevant patches applied. Several older Windows versions, including Windows Server 2016, Windows 10 version 1607, and Windows 10 version 1507, require additional registry keys to be set for all relevant SMB Multichannel fixes to be applied on fully patched installations. If you're running a version of Windows that's newer than these three versions, no additional action is required.
140-
141-
### Windows Server 2016 and Windows 10 version 1607
142-
143-
To enable all SMB Multichannel fixes for Windows Server 2016 and Windows 10 version 1607, run the following PowerShell command:
144-
145-
```PowerShell
146-
Set-ItemProperty `
147-
-Path "HKLM:SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" `
148-
-Name "2291605642" `
149-
-Value 1 `
150-
-Force
151-
```
152-
153-
### Windows 10 version 1507
154-
155-
To enable all SMB Multichannel fixes for Windows 10 version 1507, run the following PowerShell command:
156-
157-
```PowerShell
158-
Set-ItemProperty `
159-
-Path "HKLM:\SYSTEM\CurrentControlSet\Services\MRxSmb\KBSwitch" `
160-
-Name "{FFC376AE-A5D2-47DC-A36F-FE9A46D53D75}" `
161-
-Value 1 `
162-
-Force
163-
```
164-
165139
## Next steps
166140

167141
See these links for more information about Azure Files:

0 commit comments

Comments
 (0)