Merge pull request #294173 from MicrosoftDocs/main

2/6/2025 11:00 AM IST Publish

Author: PhilKang0704

articles/app-service/monitor-instances-health-check.md

@@ -74,16 +74,18 @@ If you're using your own authentication system, the Health check path must allow
 
 ```C#
 using System;
+using System.Security.Cryptography;
 using System.Text;
 
 /// <summary>
 /// Method <c>HeaderMatchesEnvVar</c> returns true if <c>headerValue</c> matches WEBSITE_AUTH_ENCRYPTION_KEY.
 /// </summary>
-public Boolean HeaderMatchesEnvVar(string headerValue) {
-    var sha = System.Security.Cryptography.SHA256.Create();
-    String envVar = Environment.GetEnvironmentVariable("WEBSITE_AUTH_ENCRYPTION_KEY");
-    String hash = System.Convert.ToBase64String(sha.ComputeHash(Encoding.UTF8.GetBytes(envVar)));
-    return hash == headerValue;
+public bool HeaderMatchesEnvVar(string headerValue)
+{
+    var sha = SHA256.Create();
+    string envVar = Environment.GetEnvironmentVariable("WEBSITE_AUTH_ENCRYPTION_KEY");
+    string hash = Convert.ToBase64String(sha.ComputeHash(Encoding.UTF8.GetBytes(envVar)));
+    return string.Equals(hash, headerValue, StringComparison.Ordinal);
 }
 ```
 

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

@@ -4,7 +4,7 @@ description: Learn how to remove TLS 1.0 and 1.1 from your application when comm
 
 
 ms.topic: conceptual
-ms.date: 12/09/2024
+ms.date: 02/05/2025
 
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 
@@ -25,15 +25,14 @@ TLS versions 1.0 and 1.1 also don't support the modern encryption methods and ci
 As a part of this effort, you can expect the following changes to Azure Cache for Redis:
 
 - _Phase 1_: Azure Cache for Redis stops offering TLS 1.0/1.1 as an option for _MinimumTLSVersion_ setting for new cache creates. Existing cache instances won't be updated at this point. You can't set the _MinimumTLSVersion_ to 1.0 or 1.1 for your existing cache.
-- _Phase 2_: Azure Cache for Redis stops supporting TLS 1.1 and TLS 1.0 starting March 1, 2025. After this change, your application must use TLS 1.2 or later to communicate with your cache. The Azure Cache for Redis service remains available while we update the _MinimumTLSVersion_ for all caches to 1.2.
-
+- _Phase 2_: Azure Cache for Redis stops supporting TLS 1.1 and TLS 1.0 starting April 1, 2025. After this change, your application must use TLS 1.2 or later to communicate with your cache. The Azure Cache for Redis service remains available while we update the _MinimumTLSVersion_ for all caches to 1.2.
 
 | Date | Description |
 |--|--|
 | September 2023 | TLS 1.0/1.1 retirement announcement |
-| 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 aren't updated automatically for existing caches at this point. |
+| 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 versions aren't updated automatically for existing caches at this point. |
 | March 31, 2025 | 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. |
-| Starting April 1, 2025 | 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. |
+| Starting April 1, 2025 | 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. |
 
 As part of this change, Azure Cache for Redis removes support for older cipher suites that aren't secure. Supported cipher suites are restricted to the following suites when the cache is configured with a minimum of TLS 1.2:
 
@@ -44,9 +43,9 @@ The following sections provide guidance about how to detect dependencies on thes
 
 ## Check TLS versions supported by your Azure Cache for Redis
 
-You can verify that **Minimum TLS version** value is set to TLS 1.2 in the [Advanced settings](cache-configure.md#advanced-settings) of your cache in the Azure portal. If it is any value other than TLS 1.2, then ensure you follow the instructions to [Configure your Azure Cache for Redis to use TLS 1.2](#configure-your-azure-cache-for-redis-to-use-tls-12). If the value is TLS 1.2, and your client application is able to connect without any errors, then no action is needed.
+You can verify that **Minimum TLS version** value is set to TLS 1.2 in the [Advanced settings](cache-configure.md#advanced-settings) of your cache in the Azure portal. If it is any value other than TLS 1.2, then ensure you follow the instructions in section [Configure your Azure Cache for Redis to use TLS 1.2](#configure-your-azure-cache-for-redis-to-use-tls-12). If the value is TLS 1.2, and your client application is able to connect without any errors, then no action is needed.
 
-You can also use this PowerShell script to verify the minimum TLS version supported by your Azure Cache for Redis endpoint. If your Redis instance is virtual network (VNet) injected, you have to run this script from a Virtual Machine in your VNet that has access to the Azure Cache for Redis endpoint. If the result shows `Tls Enabled` and/or `Tls 11 Enabled`, then ensure you follow the instructions to [Configure your Azure Cache for Redis to use TLS 1.2](#configure-your-azure-cache-for-redis-to-use-tls-12). If the result shows only `Tls12 Enabled` and your client application is able to connect without any errors, then no action is needed.
+You can also use this PowerShell script to verify the minimum TLS version supported by your Azure Cache for Redis endpoint. If your Redis instance is virtual network (VNet) injected, you have to run this script from a Virtual Machine in your VNet that has access to the Azure Cache for Redis endpoint. If the result shows `Tls Enabled` and/or `Tls 11 Enabled`, then ensure you follow the instructions in section [Configure your Azure Cache for Redis to use TLS 1.2](#configure-your-azure-cache-for-redis-to-use-tls-12). If the result shows only `Tls12 Enabled` and your client application is able to connect without any errors, then no action is needed.
 
 ```powershell
     param(
@@ -106,8 +105,6 @@ You can configure TLS 1.2 on the cache by setting the **Minimum TLS version** va
 
 1. Select **1.2** in the **Minimum TLS version** in the working pane. Then, select **Save**.
 
-  :::image type="content" source="media/cache-remove-tls-10-11/change-redis-tls-version.png" alt-text="Screenshot showing the Set TLS 1.2 for cache on Azure portal":::
-
 You can also do the same using PowerShell. You need the Az.RedisCache module already installed before running the command.
 
 ```powershell

articles/azure-cache-for-redis/media/cache-remove-tls-10-11/change-redis-tls-version.png

@@ -333,11 +333,7 @@ Application Insights (part of Azure Monitor) enables the same features in both A
 >[!NOTE]
 >Although these addresses are static, it's possible that we'll need to change them from time to time. All Application Insights traffic represents outbound traffic except for availability monitoring and webhooks, which require inbound firewall rules.
 
-You need to open some **outgoing ports** in your server's firewall to allow the Application Insights SDK and/or Status Monitor to send data to the portal:
-
-|Purpose|URL|IP address|Ports|
-|-------|---|----------|-----|
-|Telemetry|dc.applicationinsights.us|23.97.4.113|443|
+To allow the Application Insights SDK/agent to send data to the Application Insights resource, you need to allow access to the regional endpoint defined in your connection string and open the **outgoing port 443** in your firewall. To learn more about the endpoint suffix, see [Connection strings in Application Insights](/azure/azure-monitor/app/connection-strings#connection-string-with-an-endpoint-suffix).
 
 ### [Cost Management and Billing](../cost-management-billing/index.yml)
 

articles/azure-government/compare-azure-government-global-azure.md

@@ -0,0 +1,32 @@
+---
+title: Services available in Azure Communication Services
+description: Learn about the services provided by Azure Communication Services.
+author: sroons
+ms.author: serooney
+ms.service: azure-communication-services
+ms.topic: conceptual
+ms.date: 01/01/2024
+ms.custom: template-concept
+---
+
+# Services
+
+Azure Communication Services provides the following cloud-based communication and customer engagement features you can integrate with your applications.
+
+- [Identity](./identity-model.md) – The identity-agnostic model maps your existing users to Azure Communication Services identities.
+- [Chat](./chat/concepts.md) – Add real-time text communication to your cross-platform application.
+- [Email](./email/email-overview.md) – Integrate email into your application for high-volume transactional, bulk, and marketing emails.
+- [Short Message Service (SMS)](./sms/concepts.md) – Send and receive SMS text messages using SMS SDKs.
+- [Advanced messaging with WhatsApp](./advanced-messaging/whatsapp/whatsapp-overview.md) – Send and receive WhatsApp messages using the Messaging SDK.
+- [Voice and video calling](./voice-video-calling/calling-sdk-features.md) – Embed voice and video calls into websites and native applications.
+- [Phone calling](./telephony/telephony-concept.md) – Add telephony and Public Switched Telephone Network (PSTN) access to your application.
+- [Call Automation](./call-automation/call-automation.md) – Build personalized customer interaction call workflows and call recording for voice and PSTN channels.
+- [Teams interoperability](./teams-interop.md) – Enable interaction between Microsoft Teams and Azure Communication Services.
+- [Job Router](./router/concepts.md) – Manage and optimize customer interactions between different communication applications.
+- [Artificial Intelligence (AI)](./ai.md) – Add AI features such as voice bots and voice data transformation to your applications.
+- [User Interface (UI) Library](./ui-library/ui-library-overview.md) – Build modern communications user experiences using a library of production-ready UI components.
+
+## Related topics
+
+- [Common Scenarios including virtual appointments](interop/virtual-visits/overview.md)
+- [Troubleshooting in Azure Communication Services](troubleshooting-info.md)