Merge remote-tracking branch 'upstream/main' into AB#7608-Windows-update-0x8007000E

Author: v-tappelgate

Teams/phone-system/direct-routing/issues-with-call-transfers.md

@@ -15,7 +15,7 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 10/30/2023
+ms.date: 11/25/2025
 ---
 # Issues that affect call transfers
 
@@ -33,7 +33,11 @@ A call transfer can be made by using any of the following methods, in order of p
 
 All transfers that use an SIP Refer message must go through the Microsoft Teams infrastructure. When the Microsoft SIP proxy sends an SIP Refer message to SBC, an SIP Invite message should be returned to the SIP proxy, not to PSTN or to any other destination. It is true even if the call is transferred to an external PSTN number. SBC doesn't have to parse the SIP Refer message to look for the transfer target. SBC should send the SIP Invite message together with the Request-URI (RURI) setting only to contents of the Refer-To header. It also should include the Referred-By header from the SIP Refer message. Make sure that the strings of the SIP Invite message are not changed, and that they are sent as the exact same strings that are provided in the SIP Refer message (especially in the Referred-By header). This is because these strings are used to identify calls, targets, and other important parts of a call transfer.
 
-**Note:** The strings could be either x-* strings or custom strings in the Referred-By and Refer-To headers.
+**Note:** 
+
+- The strings could be either x-* strings or custom strings in the Referred-By and Refer-To headers. 
+
+- When the transfer is handled by the internal Microsoft Teams infrastructure, the transferee might hear an international ringtone.
 
 ## Auto attendant does not transfer calls to an external PSTN number
 

support/azure/azure-monitor/app-insights/availability/diagnose-ping-test-failure.md

@@ -1,9 +1,12 @@
 ---
 title: Diagnose Problems That Cause Availability Tests to Fail in Application Insights
 description: This article discusses how to diagnose common issues that cause availability tests to fail in Application Insights.
-ms.date: 8/27/2025
+author: JarrettRenshaw
+ms.author: aaronmax
+manager: dcscontentpm
+ms.date: 9/22/2025
 editor: v-jsitser
-ms.reviewer: aaronmax, cogoodson, matthofa, v-leedennis, v-weizhu, v-liuamson
+ms.reviewer: aaronmax, cogoodson, matthofa, v-leedennis, v-weizhu, v-liuamson, v-ryanberg
 ms.service: azure-monitor
 ms.custom: sap:Availability Tests
 ---
@@ -38,29 +41,27 @@ The following table lists the steps, error messages, and possible causes that yo
 |-----|---------------|----------------|
 | Connection reuse | No specific error message is returned for this issue. | The web test step is dependent on a previously established connection. Therefore, no DNS, connection, or SSL step is required. |
 | DNS resolution | The remote name could not be resolved: "\<your-URL>" | The DNS resolution process fails. This most likely occurred because of misconfigured DNS records or temporary DNS server failures. |
-| Connection establishment | A connection attempt failed because the connected party did not properly respond after a period of time. | Your server doesn't respond to the HTTP request. A common cause is that a firewall on your server is blocking our test agents. To test within an Azure Virtual Network, add the Availability service tag to your environment.|
-| TLS transport  | The client and server cannot communicate because they do not possess a common algorithm.| Only TLS 1.2, and 1.3 are supported. SSL isn't supported. This step doesn't validate SSL certificates, it only establishes a secure connection. This step appears only if an error occurs. |
+| Connection establishment | A connection attempt failed because the connected party did not properly respond after a period of time. | Your server doesn't respond to the HTTP request. A common cause is that a firewall on your server is blocking our test agents. To test within an Azure Virtual Network, add the **Availability service** tag to your environment.|
+| TLS transport  | The client and server cannot communicate because they do not possess a common algorithm.| Only TLS 1.2 and TLS 1.3 are supported. SSL isn't supported. This step doesn't validate certificates. It only establishes a secure connection and appears only if an error occurs. If you suspect a region-specific TLS 1.3 issue, see [TLS 1.3 regional restrictions](#tls-13-regional-restrictions). |
 | Receiving response header | Unable to read data from the transport connection. The connection was closed. | Your server commits a protocol error in the response header. For example, your server closes the connection if the response isn't fully read. |
-| Receiving response body | Unable to read data from the transport connection: The connection was closed. | Your server commits a protocol error in the response body. For example, your server closes the connection if the response isn't fully read, or the chunk size is wrong in the chunked response body. |
+| Receiving response body | Unable to read data from the transport connection: The connection was closed. | Your server commits a protocol error in the response body. For example, your server closes the connection if the response isn't fully read or the chunk size is wrong in the chunked response body. |
 | Redirect limit validation | This webpage has too many redirects. This loop will be terminated here since this request exceeded the limit for auto redirects. | Redirects are limited to 10 per test. |
 | Status code validation | `200 - OK` does not match the expected status `400 - BadRequest`. | The returned status code is counted as a success. The "200" code indicates that a normal web page was returned. |
-| Content validation | The required text '\<expected-response-text>' did not appear in the response. | <p>The string isn't an exact case-sensitive match in the response. For example, the string "Welcome!" must be a plain string, without wildcard characters (such as an asterisk). If your page content changes, you might have to update the string. Content match supports only English characters.</p> <p>Content match also fails if the response body is more than 1,000,000 bytes long. After the client reads that number of bytes, it stops reading the response body and drops the connection. Because of this behavior, the server experiences a `ClientConnectionFailure` exception, even if the client returns a success status code.</p> |
+| Content validation | The required text '\<expected-response-text>' did not appear in the response. | <p>The string is not an exact case-sensitive match in the response. For example, the string "Welcome!" must be a plain string, without wildcard characters (like an asterisk). If your page content changes, you might have to update the string. Content match supports only English characters.</p> <p>Content match also fails if the response body is more than 1,000,000 bytes long. After the client reads that number of bytes, it stops reading the response body and drops the connection. Because of this behavior, the server experiences a `ClientConnectionFailure` exception, even if the client returns a success status code.</p> |
 |Missing test results in Azure portal|No specific error message is returned for this issue.   Test results are missing in the Azure portal when viewing the end-to-end transaction details of an availability test. |Non-UTF8 characters aren't supported for viewing web test results. Make sure that no non-UTF8 characters exist in the response from the endpoint that's called by using the availability test.|
-|Unsupported URL|This URL is not supported|<p>Availability tests only allow communicating over publicly available IP addresses and hostnames. This error might occur when you try to communicate with an internal IP address that isn't routable via the public internet.</p> <p>To resolve this error, make sure that only public IP addresses are defined in your web test and that any DNS lookups that your web test depends on return only valid, publicly routable IP addresses.</p>|
-
-## TLS 1.3 regional restrictions
-
-Some regions restrict the use of TLS 1.3. If you experience connectivity issues in these regions, try to use an earlier version of TLS, such as TLS 1.2. For details about TLS 1.3 support, see [RFC 8446](https://datatracker.ietf.org/doc/html/rfc8446). To learn more about the supported regions, see [Supported TLS configurations](/azure/azure-monitor/app/availability?tabs=standard#supported-tls-configurations).
-
-Only TLS 1.2 and TLS 1.3 are supported. TLS 1.3 availablility varies by region. SSL is not supported. 
-
-This step doesn't validate certificates. It establishes a secure connection and only appears if an error occurs.
+|Unsupported URL|This URL is not supported|<p>Availability tests only allow communicating over publicly available IP addresses and hostnames. This error can occur when you try to communicate with an internal IP address that's not routable via the public internet.</p> <p>To resolve this error, make sure that only public IP addresses are defined in your web test and that any DNS lookups that your web test depends on return only valid, publicly routable IP addresses.</p>|
 
 > [!NOTE]
-> If the "connection reuse" step exists, the following steps won't exist:
+> If the **Connection reuse** step exists, the following steps don't appear:
 >
-> - DNS resolution
-> - Connection establishment
-> - TLS transport
+> - **DNS resolution**
+> - **Connection establishment**
+> - **TLS transport**
+
+## TLS 1.3 regional restrictions
+
+Some regions restrict the use of TLS 1.3. If you experience connectivity issues in these regions, try an earlier version of TLS, such as TLS 1.2. For details about TLS 1.3, see [RFC 8446](https://datatracker.ietf.org/doc/html/rfc8446). To learn more about the supported regions, see [Supported TLS configurations](/azure/azure-monitor/app/availability?tabs=standard#supported-tls-configurations).
 
 [!INCLUDE [Azure Help Support](../../../../includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]