Skip to content

Commit 492259c

Browse files
authored
Merge branch 'main' into Branch-CI4609
2 parents 86568a1 + c06a684 commit 492259c

193 files changed

Lines changed: 3501 additions & 1837 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.json

Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13171,6 +13171,102 @@
1317113171
{
1317213172
"source_path": "support/windows-server/active-directory/troubleshoot-domain-controller-location-issues.md",
1317313173
"redirect_url": "/troubleshoot/windows-server/windows-security/troubleshoot-domain-controller-location-issues"
13174+
},
13175+
{
13176+
"source_path": "support/windows-server/setup-upgrade-and-drivers/repair-or-in-place-upgrade.md",
13177+
"redirect_url": "/windows-server/get-started/perform-in-place-upgrade"
13178+
},
13179+
{
13180+
"source_path": "support/windows-client/user-profiles-and-logon/roaming-profile-was-not-completely-synchronized-error.md",
13181+
"redirect_url": "/previous-versions/troubleshoot/windows-client/roaming-profile-was-not-completely-synchronized-error"
13182+
},
13183+
{
13184+
"source_path": "support/windows-client/user-profiles-and-logon/renaming-user-account-not-change-profile-path.md",
13185+
"redirect_url": "/previous-versions/troubleshoot/windows-client/renaming-user-account-not-change-profile-path"
13186+
},
13187+
{
13188+
"source_path": "support/windows-client/user-profiles-and-logon/event-id-300-windows-hello-successfully-created-in-windows-10.md",
13189+
"redirect_url": "/previous-versions/troubleshoot/windows-client/event-id-300-windows-hello-successfully-created-in-windows-10"
13190+
},
13191+
{
13192+
"source_path": "support/windows-server/active-directory/convert-domain-federated.md",
13193+
"redirect_url": "/previous-versions/troubleshoot/windows-server/convert-domain-federated"
13194+
},
13195+
{
13196+
"source_path": "support/windows-server/active-directory/connection-adfs-failed-set-msoladfscontex.md",
13197+
"redirect_url": "/previous-versions/troubleshoot/windows-server/connection-adfs-failed-set-msoladfscontex"
13198+
},
13199+
{
13200+
"source_path": "support/windows-client/user-profiles-and-logon/error-invalid-store-path-loadstate-user-state-migration-tool.md",
13201+
"redirect_url": "/troubleshoot/windows-client/setup-upgrade-and-drivers/error-invalid-store-path-loadstate-user-state-migration-tool"
13202+
},
13203+
{
13204+
"source_path": "support/windows-server/active-directory/file-replication-service-event-13552-13555.md",
13205+
"redirect_url": "/troubleshoot/windows-server/networking/file-replication-service-event-13552-13555"
13206+
},
13207+
{
13208+
"source_path": "support/windows-server/active-directory/remove-orphaned-domains.md",
13209+
"redirect_url": "/troubleshoot/windows-server/windows-security/remove-orphaned-domains"
13210+
},
13211+
{
13212+
"source_path": "support/windows-server/remote/error-when-connecting-terminal-server.md",
13213+
"redirect_url": "/previous-versions/troubleshoot/windows-server/error-when-connecting-terminal-server"
13214+
},
13215+
{
13216+
"source_path": "support/dynamics-365/sales/tls-1-dot-2-required-for-connectivity.md",
13217+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/tls-1-dot-2-required-for-connectivity"
13218+
},
13219+
{
13220+
"source_path": "support/dynamics-365/sales/dynamics-crm-installations-updates-and-documentation.md",
13221+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/dynamics-crm-installations-updates-and-documentation"
13222+
},
13223+
{
13224+
"source_path": "support/dynamics-365/sales/import-of-solution-fails-due-to-missing-components.md",
13225+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import"
13226+
},
13227+
{
13228+
"source_path": "support/dynamics-365/sales/solution-install-fails-due-dependencies.md",
13229+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import"
13230+
},
13231+
{
13232+
"source_path": "support/dynamics-365/sales/error-code-8004f016-when-importing-contact-lead-attributemap.md",
13233+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13234+
},
13235+
{
13236+
"source_path": "support/dynamics-365/sales/cannot-connect-your-dynamics-365-server.md",
13237+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/cannot-connect-your-dynamics-365-server"
13238+
},
13239+
{
13240+
"source_path": "support/dynamics-365/sales/error-when-accessing-app-module.md",
13241+
"redirect_url": "/troubleshoot/power-platform/dataverse/environment-app-access/error-when-accessing-app-module"
13242+
},
13243+
{
13244+
"source_path": "support/dynamics-365/sales/solution-cannot-be-deleted.md",
13245+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/solution-cannot-be-deleted"
13246+
},
13247+
{
13248+
"source_path": "support/dynamics-365/sales/we-cannot-find-any-apps-your-role.md",
13249+
"redirect_url": "/troubleshoot/power-platform/dataverse/environment-app-access/we-cannot-find-any-apps-your-role"
13250+
},
13251+
{
13252+
"source_path": "support/dynamics-365/sales/error-code-80040203-invalid-argument-error.md",
13253+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/error-code-80040203-invalid-argument-error"
13254+
},
13255+
{
13256+
"source_path": "support/dynamics-365/sales/error-code-80048539-when-importing-solution-patch.md",
13257+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/error-code-80048539-when-importing-solution-patch"
13258+
},
13259+
{
13260+
"source_path": "support/dynamics-365/sales/error-importing-savedquery-in-dynamics-365.md",
13261+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/error-importing-savedquery-in-dynamics-365"
13262+
},
13263+
{
13264+
"source_path": "support/dynamics-365/sales/troubleshoot-dynamics365-embedcollab-issues.md",
13265+
"redirect_url": "/troubleshoot/power-platform/dataverse/microsoft-teams/troubleshoot-dynamics365-embedcollab-issues"
13266+
},
13267+
{
13268+
"source_path": "support/dynamics-365/sales/the-record-could-not-be-deleted.md",
13269+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/the-record-could-not-be-deleted"
1317413270
}
1317513271
]
1317613272
}

support/azure/.openpublishing.redirection.azure.json

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6300,9 +6300,17 @@
63006300
"source_path": "virtual-machines/linux/linux-vm-no-boot-hyper-v-driver-issues.md",
63016301
"redirect_url": "/troubleshoot/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms"
63026302
},
6303+
{
6304+
"source_path": "azure-kubernetes/create-upgrade-delete/error-code-reservedresourcename.md",
6305+
"redirect_url": "/troubleshoot/azure/azure-kubernetes/create-upgrade-delete/error-code-invalidparameter"
6306+
},
63036307
{
63046308
"source_path": "azure-kubernetes/create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md",
63056309
"redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes"
6310+
},
6311+
{
6312+
"source_path": "azure-kubernetes/create-upgrade-delete/akscapacityerror.md",
6313+
"redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/akscapacityheavyusage-error"
63066314
}
63076315
]
63086316
}

support/azure/azure-kubernetes/connectivity/cannot-access-cluster-api-server-using-authorized-ip-ranges.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: Can't access the cluster API server using authorized IP ranges
33
description: Troubleshoot problems accessing the cluster API server when you use authorized IP address ranges in Azure Kubernetes Service (AKS).
4-
ms.date: 11/18/2024
5-
ms.reviewer: chiragpa, nickoman, v-leedennis
4+
ms.date: 03/26/2025
5+
ms.reviewer: chiragpa, nickoman, wonkilee, v-leedennis
66
ms.service: azure-kubernetes-service
77
keywords:
88
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot access issues to the cluster API server when I use authorized IP address ranges so that I can work with my Azure Kubernetes Service (AKS) cluster successfully.
@@ -14,7 +14,9 @@ This article discusses how to resolve a scenario in which you can't use authoriz
1414

1515
## Symptoms
1616

17-
If you try to create or manage an AKS cluster, you can't access the cluster API server.
17+
If you try to create or manage resources in an AKS cluster, you can't access the cluster API server. When you run `kubectl`, you receive the following error message:
18+
19+
> Unable to connect to the server: dial tcp x.x.x.x:443: i/o timeout
1820
1921
## Cause
2022

support/azure/azure-kubernetes/connectivity/errors-arfter-restricting-egress-traffic.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: Errors after restricting egress traffic
33
description: Troubleshoot errors that occur after you restrict egress traffic from an Azure Kubernetes Service (AKS) cluster.
4-
ms.date: 11/12/2024
5-
ms.reviewer: chiragpa, nickoman, v-leedennis
4+
ms.date: 03/20/2025
5+
ms.reviewer: chiragpa, nickoman, jaewonpark, v-leedennis
66
ms.service: azure-kubernetes-service
77
keywords:
88
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot errors that occur after I restrict egress traffic so that I can access my AKS cluster successfully.
@@ -18,19 +18,21 @@ Certain commands of the [kubectl](https://kubernetes.io/docs/reference/kubectl/)
1818

1919
## Cause
2020

21-
When you restrict egress traffic from an AKS cluster, your settings must comply with [required Outbound network and FQDN rules for AKS clusters](/azure/aks/outbound-rules-control-egress). If your settings are in conflict with any of these rules, the symptoms of egress traffic restriction issues occur.
21+
When you restrict egress traffic from an AKS cluster, your settings must comply with required Outbound network and FQDN (fully qualified domain names) rules for AKS clusters. If your settings are in conflict with any of these rules, the egress traffic restriction issues occur.
2222

2323
## Solution
2424

25-
Verify that your configuration doesn't conflict with any of the [required Outbound network and FQDN rules for AKS clusters](/azure/aks/outbound-rules-control-egress) for the following items:
25+
Verify that your configuration doesn't conflict with any of the [required Outbound network and FQDN (fully qualified domain names) rules for AKS clusters](/azure/aks/outbound-rules-control-egress) for the following items:
2626

2727
- Outbound ports
2828
- Network rules
29-
- Fully qualified domain names (FQDNs)
29+
- FQDNs
3030
- Application rules
3131

32+
Check for conflicts with the rules that might occur in the NSG (network security group), firewall, or appliance that AKS traffic passes through according to the configuration.
33+
3234
> [!NOTE]
33-
> The AKS outbound dependencies are almost entirely defined by using FQDNs. These FQDNs don't have static addresses behind them. The lack of static addresses means that you can't use network security groups (NSGs) to restrict outbound traffic from an AKS cluster.
35+
> The AKS outbound dependencies are almost entirely defined by using FQDNs. These FQDNs don't have static addresses behind them. The lack of static addresses means that you can't use NSGs to restrict outbound traffic from an AKS cluster. Additionally, scenarios that allow only IPs that are obtained from required FQDNs after all deny in NSG are not enough to restrict outbound traffic. Because the IPs are not static, issues might occur later.
3436
3537
## More information
3638

support/azure/azure-kubernetes/connectivity/tunnel-connectivity-issues.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: Tunnel connectivity issues
33
description: Resolve communication issues that are related to tunnel connectivity in an Azure Kubernetes Service (AKS) cluster.
4-
ms.date: 09/26/2024
5-
ms.reviewer: chiragpa, andbar, v-leedennis, v-weizhu
4+
ms.date: 03/23/2025
5+
ms.reviewer: chiragpa, andbar, v-leedennis, v-weizhu, albarqaw
66
ms.service: azure-kubernetes-service
77
keywords: Azure Kubernetes Service, AKS cluster, Kubernetes cluster, tunnels, connectivity, tunnel-front, aks-link
88
#Customer intent: As an Azure Kubernetes user, I want to avoid tunnel connectivity issues so that I can use an Azure Kubernetes Service (AKS) cluster successfully.

support/azure/azure-kubernetes/create-upgrade-delete/akscapacityerror.md

Lines changed: 0 additions & 71 deletions
This file was deleted.

support/azure/azure-kubernetes/create-upgrade-delete/error-code-inuseroutetablecannotbedeleted.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
title: Troubleshoot the InUseRouteTableCannotBeDeleted error code
33
description: Learn how to troubleshoot the InUseRouteTableCannotBeDeleted error when you try to delete an Azure Kubernetes Service (AKS) cluster.
4-
ms.date: 11/12/2024
4+
ms.date: 03/28/2025
55
editor: v-jsitser
6-
ms.reviewer: rissing, chiragpa, edneto, v-leedennis
6+
ms.reviewer: rissing, chiragpa, edneto, wonkilee, v-leedennis
77
ms.service: azure-kubernetes-service
88
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the InUseRouteTableCannotBeDeleted error code so that I can successfully delete an Azure Kubernetes Service (AKS) cluster.
99
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -30,6 +30,6 @@ You tried to delete the AKS cluster while its associated route table was still i
3030

3131
## Solution
3232

33-
Remove the associated subnet in the route table. For instructions, see [Dissociate a route table from a subnet](/azure/virtual-network/manage-route-table#dissociate-a-route-table-from-a-subnet). Then, try again to delete the AKS cluster.
33+
Remove the associated route table from the subnet. For instructions, see [Dissociate a route table from a subnet](/azure/virtual-network/manage-route-table#dissociate-a-route-table-from-a-subnet). Then, try again to delete the AKS cluster.
3434

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

support/azure/azure-kubernetes/create-upgrade-delete/error-code-reservedresourcename.md

Lines changed: 0 additions & 37 deletions
This file was deleted.

0 commit comments

Comments
 (0)