Skip to content

Commit c36a393

Browse files
author
gitName
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into wsws
2 parents 677b090 + 8da0465 commit c36a393

File tree

11 files changed

+412
-383
lines changed

11 files changed

+412
-383
lines changed

articles/communication-services/concepts/voice-video-calling/real-time-text.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.subservice: calling
1616
# Real Time Text (RTT) Overview
1717

1818
>[!NOTE]
19-
>RTT is an accessibility compliance requirement for voice and video platforms in the EU. You can find more information about this here: [Directive 2019/882](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019L0882)
19+
>RTT is an accessibility compliance requirement for voice and video platforms in the EU starting June 30, 2025. You can find more information about this here: [Directive 2019/882](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019L0882)
2020
2121
Real Time Text (RTT) provides developers with the ability to transmit text in near real-time during a call. This feature is designed to empower individuals who have difficulty speaking, ensuring their text messages are displayed prominently to other meeting participants, similar to spoken communication. RTT enhances accessibility by allowing participants to communicate effectively through typed messages that are broadcast instantly character by character, without having to press a "send" key.
2222

@@ -53,6 +53,9 @@ The `RealTimeTextInfo` (or `RealTimeTextDetails` on certain platforms) class is
5353

5454
Developers can subscribe to RTT events through a single event subscription, allowing them to manage their own list and ordering of RTT messages. This approach aligns with the Captions API, facilitating easier integration and maintenance. The UI is responsible for binding the data to the screen, managing the display list, and handling text input interactions based on message finalization.
5555

56+
>[!NOTE]
57+
>RTT Teams Interlop is not functional yet.
58+
5659
### Privacy Concerns
5760
Real-Time Text (RTT) is only available during the call or meeting. Azure Communication Services doesn't store these text exchanges anywhere. Many countries/regions and states have laws and regulations that apply to the storing of data. It is your responsibility to use RTT in compliance with the law should you choose to store any of the data generated through RTT. You must obtain consent from the parties involved in a manner that complies with the laws applicable to each participant.
5861

articles/communication-services/quickstarts/voice-video-calling/get-started-with-real-time-text.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,13 @@ zone_pivot_groups: acs-programming-languages-java-swift-csharp
1414

1515

1616

17-
# Real Time Text
17+
# Quickstart RTT within your application
1818

1919
[!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include-document.md)]
2020

21+
>[!NOTE]
22+
>RTT is an accessibility compliance requirement for voice and video platforms in the EU starting June 30, 2025. You can find more information about this here: [Directive 2019/882](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019L0882).
23+
2124
Learn how to integrate Real Time Text (RTT) into your calling applications to enhance accessibility and ensure that all participants can communicate effectively during meetings.
2225

2326
RTT allows users who have difficulty speaking to participate actively by typing their messages, which are then broadcast in near real-time to other meeting participants. This feature operates seamlessly alongside existing captions and ensures that typed messages are promptly delivered without disrupting the flow of conversation.
@@ -28,6 +31,9 @@ Real Time Text (RTT) is designed to facilitate communication for users who may h
2831

2932
On supported platforms, RTT data can be displayed alongside captions derived from Speech to Text, providing a comprehensive view of all communications during a call.
3033

34+
>[!NOTE]
35+
>RTT Teams Interlop is not functional yet.
36+
3137
## Naming Conventions
3238

3339
Different platforms may use varying terminology for RTT-related properties. Below is a summary of these differences:
@@ -70,5 +76,5 @@ The `RealTimeTextInfo` (or `RealTimeTextDetails` on Windows) class encapsulates
7076
## Next steps
7177

7278
For more information, see the following articles:
73-
79+
- [Real Time Text Conceptual Doc](../../concepts/voice-video-calling/real-time-text.md)
7480
- [Azure Communication Services Calling Documentation](../../concepts/voice-video-calling/calling-sdk-features.md)

articles/databox-online/azure-stack-edge-gpu-configure-tls-settings.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,14 +9,14 @@ metadata:
99

1010
ms.service: azure-stack-edge
1111
ms.topic: how-to
12-
ms.date: 03/21/2024
12+
ms.date: 02/27/2025
1313
ms.author: alkohli
1414
title: |
1515
Configure TLS 1.2 on Windows clients accessing Azure Stack Edge Pro device
1616
introduction: |
1717
[!INCLUDE [applies-to-GPU-and-pro-r-and-mini-r-skus](../../includes/azure-stack-edge-applies-to-gpu-pro-r-mini-r-sku.md)]
1818
19-
If you are using a Windows client to access your Azure Stack Edge Pro device, you are required to configure TLS 1.2 on your client. This article provides resources and guidelines to configure TLS 1.2 on your Windows client.
19+
If you use a Windows client to access your Azure Stack Edge Pro device, you are required to configure TLS 1.2 on your client. This article provides resources and guidelines to configure TLS 1.2 on your Windows client.
2020
2121
The guidelines provided here are based on testing performed on a client running Windows Server 2016.
2222
prerequisites:

articles/openshift/howto-infrastructure-nodes.md

Lines changed: 33 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -213,6 +213,39 @@ Vnet:
213213
oc get machineset <machineset_name> -n openshift-machine-api -o jsonpath='{.spec.template.spec.providerSpec.value.vnet}'
214214
```
215215
216+
## DNS
217+
218+
Follow the instructions below to enable scheduling of DNS pods on the infrastructure nodes.
219+
220+
> [!NOTE]
221+
> This section is crucial to support log collection from infrastructure nodes, ensuring supportability of your deployment.
222+
>
223+
224+
1. Allow the DNS pods to run on the infrastructure nodes.
225+
226+
```
227+
oc edit dns.operator/default
228+
```
229+
230+
```
231+
apiVersion: operator.openshift.io/v1
232+
kind: DNS
233+
metadata:
234+
name: default
235+
spec:
236+
nodePlacement:
237+
tolerations:
238+
- operator: Exists
239+
```
240+
241+
1. Verify that DNS pods are scheduled onto all infra nodes.
242+
243+
```
244+
oc get ds/dns-default -n openshift-dns
245+
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
246+
dns-default 7 7 7 7 7 kubernetes.io/os=linux 35d
247+
```
248+
216249
## Moving workloads to the new infrastructure nodes
217250
218251
Use the instructions below to move your infrastructure workloads to the infrastructure nodes previously created.
@@ -359,30 +392,4 @@ Use this procedure for any additional ingress controllers you may have in the cl
359392
kube-state-metrics-574c5bfdd7-f7fjk 3/3 Running 0 2m49s 10.131.4.8 cz-cluster-hsmtw-infra-aro-machinesets-eastus-1-vr56r <none> <none>
360393
```
361394
362-
### DNS
363-
364-
1. Allow the DNS pods to run on the infrastructure nodes.
365-
366-
```
367-
oc edit dns.operator/default
368-
```
369-
370-
```
371-
apiVersion: operator.openshift.io/v1
372-
kind: DNS
373-
metadata:
374-
name: default
375-
spec:
376-
nodePlacement:
377-
tolerations:
378-
- operator: Exists
379-
```
380-
381-
1. Verify that DNS pods are scheduled onto all infra nodes.
382-
383-
```
384-
oc get ds/dns-default -n openshift-dns
385-
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
386-
dns-default 7 7 7 7 7 kubernetes.io/os=linux 35d
387-
```
388395

articles/reliability/availability-zones-migration-overview.md

Lines changed: 42 additions & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -5,82 +5,55 @@ author: anaharris-ms
55
ms.service: azure
66
ms.subservice: azure-reliability
77
ms.topic: conceptual
8-
ms.date: 11/08/2022
8+
ms.date: 02/27/2025
99
ms.author: anaharris
1010
ms.custom: subject-reliability
1111
---
1212

13-
# Availability zone migration guidance overview for Microsoft Azure products and services
13+
# Availability zone migration guidance overview
1414

15-
Azure services that support availability zones, including zonal and zone-redundant offerings, are continually expanding. For that reason, resources that don't currently have availability zone support, may have an opportunity to gain that support. The Migration Guides section offers a collection of guides for each service that requires certain procedures in order to move a resource from non-availability zone support to availability support. You'll find information on prerequisites for migration, download requirements, important migration considerations and recommendations.
15+
To improve the reliability of your solution, it's a good practice to enable availability zone support on your Azure resources. Most services require that you follow certain procedures in order to enable availability zone support on an existing resource. In the list below, you'll find guides to support availability zones on many Azure services. These guides provide detailed information such as prerequisites for migration, expected downtime, important migration considerations, and recommendations.
1616

17-
The table below lists each product that offers migration guidance and/or information.
1817

1918
## Azure services migration guides
2019

21-
### ![An icon that signifies this service is foundational.](media/icon-foundational.svg) Foundational services
2220

23-
| **Products** |
24-
| --- |
25-
| [Azure Application Gateway (V2)](migrate-app-gateway-v2.md) |
26-
| [Azure Backup and Azure Site Recovery](migrate-recovery-services-vault.md) |
27-
| [Azure ExpressRoute](/azure/expressroute/expressroute-howto-gateway-migration-portal) |
28-
| [Azure Functions](migrate-functions.md)|
29-
| [Azure Load Balancer](migrate-load-balancer.md)|
30-
| [Azure Service Fabric](migrate-service-fabric.md) |
31-
| [Azure SQL Database](migrate-sql-database.md) |
32-
| [Azure Storage account: Blob Storage, Azure Data Lake Storage, Files Storage](migrate-storage.md) |
33-
| [Azure Storage: Managed Disks](migrate-vm.md)|
34-
| [Azure Virtual Machines and Azure Virtual Machine Scale Sets](migrate-vm.md)|
35-
36-
37-
\*VMs that support availability zones: AV2-series, B-series, DSv2-series, DSv3-series, Dv2-series, Dv3-series, ESv3-series, Ev3-series, F-series, FS-series, FSv2-series, and M-series.
38-
39-
### ![An icon that signifies this service is mainstream.](media/icon-mainstream.svg) Mainstream services
40-
41-
| **Products** |
42-
| --- |
43-
| [Azure API Management](migrate-api-mgt.md)|
44-
| [Azure App Configuration](migrate-app-configuration.md)|
45-
| [Azure App Service](reliability-app-service.md#availability-zone-support)|
46-
| [Azure Batch](reliability-batch.md#availability-zone-migration)|
47-
| [Azure Cache for Redis](migrate-cache-redis.md)|
48-
| [Azure AI Search](migrate-search-service.md)|
49-
| [Azure Container Apps](reliability-azure-container-apps.md#availability-zone-migration)|
50-
| [Azure Container Instances](migrate-container-instances.md)|
51-
| [Azure Container Registry](/azure/container-registry/zone-redundancy?toc=/azure/reliability) |
52-
| [Azure Cosmos DB](/azure/cosmos-db/high-availability?toc=/azure/reliability) |
53-
| [Azure Database for MySQL - Flexible Server](migrate-database-mysql-flex.md)|
54-
| [Azure Database for PostgreSQL](/azure/postgresql/flexible-server/how-to-manage-high-availability-portal#enable-high-availability-during-server-creation)|
55-
| [Azure Elastic SAN](reliability-elastic-san.md#availability-zone-migration)|
56-
| [Azure Functions](reliability-functions.md#availability-zone-migration)|
57-
| [Azure HDInsight](reliability-hdinsight.md#availability-zone-migration)|
58-
| [Azure Kubernetes Service](/azure/aks/availability-zones?toc=/azure/reliability)|
59-
| [Azure Logic Apps](/azure/logic-apps/set-up-zone-redundancy-availability-zones?tabs=standard&toc=/azure/reliability)|
60-
| [Azure Monitor: Log Analytics](migrate-monitor-log-analytics.md)|
61-
| [Azure Service Bus](/azure/service-bus-messaging/service-bus-outages-disasters#availability-zones)|
62-
| [Azure SQL Managed Instance](migrate-sql-managed-instance.md)|
63-
64-
65-
66-
## Workload and general guidance
67-
| **Workloads** |
68-
| --- |
69-
| [Azure Kubernetes Service (AKS) and MySQL Flexible Server](migrate-workload-aks-mysql.md)|
70-
71-
## Next steps
72-
73-
> [!div class="nextstepaction"]
74-
> [Azure services with availability zones](availability-zones-service-support.md)
75-
76-
> [!div class="nextstepaction"]
77-
> [Azure regions with availability zones](availability-zones-region-support.md)
78-
79-
> [!div class="nextstepaction"]
80-
> [Availability of service by category](availability-service-by-category.md)
81-
82-
> [!div class="nextstepaction"]
83-
> [Microsoft commitment to expand Azure availability zones to more regions](https://azure.microsoft.com/blog/our-commitment-to-expand-azure-availability-zones-to-more-regions/)
84-
85-
> [!div class="nextstepaction"]
86-
> [Build solutions for high availability using availability zones](/azure/architecture/high-availability/building-solutions-for-high-availability)
21+
- [Azure API Management](migrate-api-mgt.md)
22+
- [Azure App Configuration](migrate-app-configuration.md)
23+
- [Azure App Service](reliability-app-service.md#configure-availability-zone-support)
24+
- [Azure Application Gateway (V2)](migrate-app-gateway-v2.md)
25+
- [Azure Backup and Azure Site Recovery](migrate-recovery-services-vault.md)
26+
- [Azure Batch](reliability-batch.md#availability-zone-migration)
27+
- [Azure Cache for Redis](migrate-cache-redis.md)
28+
- [Azure Container Apps](reliability-azure-container-apps.md#availability-zone-migration)
29+
- [Azure Container Instances](./reliability-containers.md#availability-zone-redeployment-and-migration)
30+
- [Azure Container Registry](/azure/container-registry/zone-redundancy?toc=/azure/reliability)
31+
- [Azure Cosmos DB](./reliability-cosmos-db-nosql.md#migrate-to-availability-zone-support)
32+
- [Azure Database for MySQL - Flexible Server](migrate-database-mysql-flex.md)
33+
- [Azure Database for PostgreSQL](./reliability-postgresql-flexible-server.md#availability-zone-redeployment-and-migration)
34+
- [Azure Elastic SAN](reliability-elastic-san.md#availability-zone-migration)
35+
- [Azure ExpressRoute](/azure/expressroute/expressroute-howto-gateway-migration-portal)
36+
- [Azure Functions](reliability-functions.md#availability-zone-migration)
37+
- [Azure HDInsight](reliability-hdinsight.md#availability-zone-migration)
38+
- [Azure Kubernetes Service](/azure/aks/availability-zones?toc=/azure/reliability)
39+
- [Azure Kubernetes Service (AKS) and MySQL Flexible Server](migrate-workload-aks-mysql.md)
40+
- [Azure Load Balancer](migrate-load-balancer.md)
41+
- [Azure Logic Apps](./reliability-logic-apps.md#configure-availability-zone-support)
42+
- [Azure Monitor: Log Analytics](migrate-monitor-log-analytics.md)
43+
- [Azure Service Bus](/azure/service-bus-messaging/service-bus-outages-disasters#availability-zones)
44+
- [Azure Service Fabric](migrate-service-fabric.md)
45+
- [Azure SQL Database](migrate-sql-database.md)
46+
- [Azure SQL Managed Instance](migrate-sql-managed-instance.md)
47+
- [Azure Storage account: Blob Storage, Azure Data Lake Storage, Files Storage](migrate-storage.md)
48+
- [Azure Storage: Managed Disks](migrate-vm.md)
49+
- [Azure Virtual Machines and Azure Virtual Machine Scale Sets](migrate-vm.md)
50+
51+
52+
53+
54+
## Related resources
55+
- [Azure reliability guides](overview-reliability-guidance.md)
56+
- [Azure services with availability zones](availability-zones-service-support.md)
57+
- [Azure regions with availability zones](availability-zones-region-support.md)
58+
- [Microsoft commitment to expand Azure availability zones to more regions](https://azure.microsoft.com/blog/our-commitment-to-expand-azure-availability-zones-to-more-regions/)
59+
- [Recommendations for using availability zones and regions](/azure/well-architected/reliability/regions-availability-zones)

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

Lines changed: 3 additions & 3 deletions
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: 11/04/2024
7+
ms.date: 02/27/2025
88
ms.author: kendownie
99
ms.custom: devx-track-azurepowershell
1010
---
@@ -57,9 +57,9 @@ Azure Files offers multiple settings that affect the behavior, performance, and
5757
SMB Multichannel enables an SMB 3.x client to establish multiple network connections to an SMB file share. Azure Files supports SMB Multichannel on premium file shares (file shares in the FileStorage storage account kind). There is no additional cost for enabling SMB Multichannel in Azure Files. SMB Multichannel is now enabled by default in all Azure regions.
5858

5959
# [Portal](#tab/azure-portal)
60-
To view the status of SMB Multichannel, navigate to the storage account containing your premium file shares and select **File shares** under the **Data storage** heading in the storage account table of contents. The status of the SMB Multichannel can be seen under the **File share settings** section.
60+
To view the status of SMB Multichannel, navigate to the storage account containing your premium file shares and select **File shares** under the **Data storage** heading in the storage account table of contents. You should see the status of SMB Multichannel under the **File share settings** section. If you don't see it, make sure your storage account is of the FileStorage account kind.
6161

62-
![A screenshot of the file shares section with in the storage account highlighting the SMB Multichannel setting](./media/files-smb-protocol/1-smb-multichannel-enable.png)
62+
:::image type="content" source="media/files-smb-protocol/smb-multichannel-enabled.png" alt-text="A screenshot of the file shares section within the storage account highlighting the SMB Multichannel setting." lightbox="media/files-smb-protocol/smb-multichannel-enabled.png":::
6363

6464
To enable or disable SMB Multichannel, select the current status (**Enabled** or **Disabled** depending on the status). The resulting dialog provides a toggle to enable or disable SMB Multichannel. Select the desired state and select **Save**.
6565

Binary file not shown.
77.7 KB
Loading

articles/virtual-network/toc.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -230,6 +230,8 @@
230230
href: ./security-controls-policy.md
231231
- name: Azure security baseline for Virtual Network
232232
href: /azure/baselines/virtual-network-security-baseline?toc=%2Fazure%2Fvirtual-network%2Ftoc.json
233+
- name: Azure Security blog
234+
href: https://techcommunity.microsoft.com/category/azure-network-security/blog/azurenetworksecurityblog
233235
- name: DDoS protection
234236
items:
235237
- name: Overview
@@ -289,8 +291,8 @@
289291
items:
290292
- name: Build your skills with Microsoft Learn training
291293
href: /training/browse/
292-
- name: Networking blog
293-
href: https://azure.microsoft.com/blog/category/networking
294+
- name: Azure Networking blog
295+
href: https://techcommunity.microsoft.com/category/azure/blog/azurenetworkingblog
294296
- name: Networking feedback
295297
href: https://feedback.azure.com/d365community/forum/8ae9bf04-8326-ec11-b6e6-000d3a4f0789
296298
- name: Pricing

0 commit comments

Comments
 (0)