Skip to content

Commit c4dc1d1

Browse files
authored
Merge branch 'main' into v-lianna-patch-27
2 parents 7b8eca7 + 0d182c7 commit c4dc1d1

2,028 files changed

Lines changed: 8771 additions & 2447 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.openpublishing.redirection.developer.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5842,6 +5842,10 @@
58425842
{
58435843
"source_path": "support/developer/webapps/iis/www-administration-management/http-bad-request-response-kerberos.md",
58445844
"redirect_url": "/troubleshoot/developer/webapps/iis/www-authentication-authorization/http-bad-request-response-kerberos"
5845+
},
5846+
{
5847+
"source_path": "support/developer/webapps/iis/health-diagnostic-performance/troubleshoot-native-memory-leak-iis-7x-application-pool.md",
5848+
"redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/troubleshoot-native-memory-leak-iis-7x-application-pool"
58455849
}
58465850
]
58475851
}

.openpublishing.redirection.json

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6915,11 +6915,6 @@
69156915
"redirect_url": "/previous-versions/troubleshoot/windows-server/windows-virtual-desktop-blank-screen",
69166916
"redirect_document_id": false
69176917
},
6918-
{
6919-
"source_path": "support/azure/virtual-desktop/welcome-virtual-desktop.yml",
6920-
"redirect_url": "/azure/virtual-desktop",
6921-
"redirect_document_id": false
6922-
},
69236918
{
69246919
"source_path": "support/windows-client/windows-troubleshooters/introduction-to-troubleshootingscript-toolset-tss.md",
69256920
"redirect_url": "/troubleshoot/windows-client/windows-tss/introduction-to-troubleshootingscript-toolset-tss",

support/azure/automation/updates/find-azurermresource-fails.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,6 @@ Starting in Microsoft AzureRM 6.0.0, the `Find-AzureRmResource` cmdlet functiona
2525

2626
## Resolution
2727

28-
To fix this issue, update your runbooks to use `Get-AzureRmResource` instead of `Find-AzureRmResource`. For more information, see the [usage of Get-AzureRmResource](/powershell/module/azurerm.resources/get-azurermresource?view=azurermps-6.1.0&preserve-view=true).
28+
To fix this issue, update your runbooks to use `Get-AzureRmResource` instead of `Find-AzureRmResource`. For more information, see the [usage of Get-AzureRmResource](/previous-versions/powershell/module/azurerm.resources/get-azurermresource).
2929

3030
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-functions/monitoring/functions-monitoring-appinsightslogs.md

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: Application Insights logs are missing or incorrect
33
description: Ths article helps you resolve issues related to missing or incorrect logs for Application Insights logs in Azure Functions.
4-
ms.date: 08/24/2023
5-
ms.reviewer: gasridha, v-jayaramanp
4+
ms.date: 01/16/2025
5+
ms.reviewer: gasridha, v-jayaramanp, agaltrai, jarrettr
66
ms.custom: sap:Monitoring using Application Insights, Metrics and Alerts
77
---
88

@@ -30,6 +30,23 @@ If the Application Insights logs are missing, or if the data appears to be parti
3030

3131
**Recommendation**: The function app should be on version 4 and the runtime version should be at least 4.15.2*xx*. This is because, from this version onwards, you can track the log flows from Azure Functions to the Application Insights service. By monitoring the log flows, you can check for missing logs.
3232

33+
## Custom application logs
34+
35+
By default, custom application logs you write are sent to the Functions host, which then sends them to Application Insights under the [Worker category](/azure/azure-functions/configure-monitoring#configure-categories). However, some language stacks allow you to send the logs directly to Application Insights, which gives you full control over how logs you write are emitted. In this case, the logging pipeline changes from `worker > Functions host > Application Insights` to `worker > Application Insights`.
36+
37+
The following table summarizes the configuration options available for each stack:
38+
39+
| Language stack | Where to configure custom logs |
40+
|-|-|
41+
| .NET (in-process model) | `host.json` |
42+
| .NET (isolated model) | Default (send custom logs to the Functions host): `host.json`<br/>To send logs directly to Application Insights, see [Configure Application Insights in the HostBuilder](/azure/azure-functions/dotnet-isolated-process-guide#application-insights). |
43+
| Node.JS | `host.json` |
44+
| Python | `host.json` |
45+
| Java | Default (send custom logs to the Functions host): `host.json`<br/>To send logs directly to Application Insights, see [Configure the Application Insights Java agent](/azure/azure-monitor/app/monitor-functions#distributed-tracing-for-java-applications). |
46+
| PowerShell | `host.json` |
47+
48+
When you configure custom application logs to be sent directly, the host no longer emits them, and `host.json` no longer controls their behavior. Similarly, the options exposed by each stack apply only to custom logs, and they don't change the behavior of the other runtime logs described in this article. In this case, to control the behavior of all logs, you might need to make changes in both configurations.
49+
3350
## Logs are missing or partial
3451

3552
Application Insights collects log, performance, and error data. [Sampling configuration](/azure/azure-functions/configure-monitoring#configure-sampling) is used to reduce the volume of telemetry. The Sampling feature is enabled by default with the settings shown in the following [host.json](/azure/azure-functions/functions-host-json#applicationinsights) example. Excluded types aren't sampled.

support/azure/azure-kubernetes/extensions/troubleshoot-failed-kubernetes-deployment-offer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ You can use the Azure CLI commands that are described in the [Azure CLI legal te
132132
133133
#### [PowerShell](#tab/PowerShell)
134134
135-
To accept the legal terms through PowerShell, run the cmdlets that are described in the [PowerShell legal terms](/powershell/module/azurerm.marketplaceordering).
135+
To accept the legal terms through PowerShell, run the cmdlets that are described in the [PowerShell legal terms](/powershell/module/az.marketplaceordering).
136136
137137
---
138138

support/azure/index.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,11 @@ productDirectory:
114114
links:
115115
- url: site-recovery/welcome-site-recovery.yml
116116
text: Troubleshooting articles for Site Recovery
117+
- title: Azure Virtual Desktop
118+
imageSrc: "https://learn.microsoft.com/static/ui/media/product/azure/virtual-desktop.svg"
119+
links:
120+
- url: virtual-desktop/welcome-virtual-desktop.yml
121+
text: Troubleshoot common Azure Virtual Desktop issues
117122
- title: Virtual Machines
118123
imageSrc: "https://static.docs.com/ui/media/product/azure/virtual-machine.svg"
119124
links:

support/azure/synapse-analytics/dedicated-sql/connectivity/dsql-conn-dropped-connections.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The following PowerShell script downloads and runs the latest version of the Azu
3838

3939
> [!NOTE]
4040
> - To run the tests in Linux, from computers that have no Internet access, or from a containerized environment, see [SQL connectivity checker on GitHub](https://github.com/Azure/SQL-Connectivity-Checker).
41-
> - For more PowerShell commands, see [Available PowerShell commands](/powershell/module/azurerm.sql#sql).
41+
> - For more PowerShell commands, see [Available PowerShell commands](/powershell/module/az.sql#sql).
4242
4343
1. Open Windows PowerShell ISE (in **Administrator** mode if possible).
4444
> [!NOTE]
Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
3+
ms.reviewer: daknappe
4+
ms.topic: include
5+
ms.date: 11/21/2022
6+
---
7+
8+
### Your account is configured to prevent you from using this device
9+
10+
If you come across an error saying **Your account is configured to prevent you from using this device. For more information, contact your system administrator**, ensure the user account was given the [Virtual Machine User Login role](/entra/identity/devices/howto-vm-sign-in-azure-ad-windows#azure-role-not-assigned) on the VMs.
11+
12+
### The user name or password is incorrect
13+
14+
If you can't sign in and keep receiving an error message that says your credentials are incorrect, first make sure you're using the right credentials. If you keep seeing error messages, check to make sure you've fulfilled the following requirements:
15+
16+
- Have you assigned the **Virtual Machine User Login** role-based access control (RBAC) permission to the virtual machine (VM) or resource group for each user?
17+
- Does your Conditional Access policy exclude multifactor authentication requirements for the **Azure Windows VM sign-in** cloud application?
18+
19+
If you've answered no to either of those questions, you'll need to reconfigure your multifactor authentication. To reconfigure your multifactor authentication, follow the instructions in [Enforce Microsoft Entra multifactor authentication for Azure Virtual Desktop using Conditional Access](/azure/virtual-desktop/set-up-mfa?tabs=avd#azure-ad-joined-session-host-vms#azure-ad-joined-session-host-vms).
20+
21+
> [!IMPORTANT]
22+
> VM sign-ins don't support per-user enabled or enforced Microsoft Entra multifactor authentication. If you try to sign in with multifactor authentication on a VM, you won't be able to sign in and will receive an error message.
23+
24+
If you have [integrated Microsoft Entra logs with Azure Monitor logs](/entra/identity/monitoring-health/howto-integrate-activity-logs-with-azure-monitor-logs) to access your Microsoft Entra sign-in logs through Log Analytics, you can see if you've enabled multifactor authentication and which Conditional Access policy is triggering the event. The events shown are non-interactive user login events for the VM, which means the IP address will appear to come from the external IP address from which your VM accesses Microsoft Entra ID.
25+
26+
You can access your sign-in logs by running the following Kusto query:
27+
28+
```kusto
29+
let UPN = "userupn";
30+
AADNonInteractiveUserSignInLogs
31+
| where UserPrincipalName == UPN
32+
| where AppId == "372140e0-b3b7-4226-8ef9-d57986796201"
33+
| project ['Time']=(TimeGenerated), UserPrincipalName, AuthenticationRequirement, ['MFA Result']=ResultDescription, Status, ConditionalAccessPolicies, DeviceDetail, ['Virtual Machine IP']=IPAddress, ['Cloud App']=ResourceDisplayName
34+
| order by ['Time'] desc
35+
```
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
3+
ms.reviewer: daknappe
4+
ms.topic: include
5+
ms.date: 11/21/2022
6+
---
7+
8+
### Error code 2607 - We couldn't connect to the remote PC because your credentials did not work
9+
10+
If you come across an error saying **We couldn't connect to the remote PC because your credentials did not work. The remote machine is AADJ joined.** with error code 2607 when using the Android client, ensure that you [enabled connections from other clients](/entra/identity/devices/howto-vm-sign-in-azure-ad-windows#connect-using-the-other-clients).
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
3+
ms.reviewer: daknappe
4+
ms.topic: include
5+
ms.date: 11/21/2022
6+
---
7+
8+
### Sign in failed. Please check your username and password and try again
9+
10+
If you come across an error saying **Oops, we couldn't connect to *NAME*. Sign in failed. Please check your username and password and try again.** when using the web client, ensure that you [enabled connections from other clients](/entra/identity/devices/howto-vm-sign-in-azure-ad-windows#connect-using-the-other-clients).
11+
12+
### We couldn't connect to the remote PC because of a security error
13+
14+
If you come across an error saying **Oops, we couldn't connect to *NAME*. We couldn't connect to the remote PC because of a security error. If this keeps happening, ask your admin or tech support for help.**, you have Conditional Access policies restricting access. Follow the instructions in [Enforce Microsoft Entra multifactor authentication for Azure Virtual Desktop using Conditional Access](/azure/virtual-desktop/set-up-mfa?tabs=avd#azure-ad-joined-session-host-vms#azure-ad-joined-session-host-vms) to enforce Microsoft Entra multifactor authentication for your Microsoft Entra joined VMs.

0 commit comments

Comments
 (0)