DOCSEARCHbyAlgolia
Submit Docs

Microsoft Support Articles

repository·main·Indexed 42 days ago

https://github.com/microsoftdocs/supportarticles-docs

Technical support documentation and troubleshooting guides for Microsoft products, including Microsoft Purview Data Loss Prevention (DLP), Exchange Online, Exchange Server (2016, 2019, and SE), and hybrid deployments.

Tokens
260.8K
Snippets
425
Records
1K
Agent score
54%

What's inside Microsoft Support Articles

  1. Troubleshoot AKS cluster extension deployment errors

    main

    When deploying cluster extensions for Azure Kubernetes Service (AKS), errors typically fall into two categories: Core extensions (like Azure Monitor) or Standard extensions/Kubernetes applications (deployed via Helm).

    To troubleshoot, first identify which category your extension belongs to:

    1. Core Extensions (e.g., Azure Monitor)

    Common issues include:

    • Provisioning state is Failed: The extension failed to deploy.
    • Direct extension update is denied: You are unable to edit or update the monitoring extension directly.
    • Resource locks: A lock is preventing you from disabling the monitoring add-on.
    • Azure Policy: An Azure Policy is blocking the enablement of the monitoring add-on.

    2. Standard Extensions or Kubernetes Applications (Helm-based)

    Common issues include:

    • Resource readiness timeout or BackoffLimitExceeded.
    • Helm chart download failures from the repository URL.
    • Helm chart rendering failures due to provided values.
    • Resource conflicts: An existing Kubernetes resource already exists in the cluster.
    • Concurrent operations: Another Helm operation is already in progress.

  2. Alternative debugging approaches for Canvas Apps

    main

    When Live monitor is unsupported (e.g., in SharePoint integrated forms, custom pages, or custom portal embeddings) or when debugging intermittent issues, use one of these four alternative methods:

    AlternativeBest forNotes
    Application InsightsCentralized telemetry and performance monitoringRequires Azure setup. Emits traces and metrics outside Power Apps.
    Dataverse logging tableAd-hoc diagnostics and audit trailsCreate a custom table. Use guarded logic to write records when debugging.
    SharePoint list loggingLightweight environments without DataverseUse Collect or Patch to write to a list. To control size, prune entries.
    On-screen diagnostics panelImmediate feedback during testingOnly for secure audiences. Remove before a broad rollout.

  3. Upgrade RHEL pay-as-you-go virtual machines using Leapp

    main

    This guide describes how to use the Leapp utility to perform in-place upgrades for Red Hat Enterprise Linux (RHEL) pay-as-you-go virtual machines on Azure. Supported upgrade paths include:

    • RHEL 7 to RHEL 8
    • RHEL 8 to RHEL 9
    • RHEL 9 to RHEL 10
    CAUTION

    Performing an in-place upgrade causes a disconnection between the VM's data plane and the Azure control plane. Consequently, the following Azure features will not be available:

    • Automatic guest patching
    • Automatic operating system (OS) image upgrades
    • Hotpatching
    • Azure Update Manager

    If you require these features, you should create a new VM with your preferred OS instead of performing an in-place upgrade.

  4. New features in Management Reporter 2012 CU14

    main

    Cumulative Update 14 (CU14) introduces several new features and enhancements:

    • Web Viewer (Data Mart only): Users can change the Period and regenerate reports directly from the Web Viewer.
    • Keyboard Accessibility: Added keyboard accessibility for the 'Drill to Dynamics' feature.
    • Microsoft Dynamics AX 2012 Enhancements:
      • Support for budget submodels with multiple parents.
      • Budget Control enhancements including new attributes.
    • Microsoft Dynamics GP: Performance improvements (previously released as CU13 hotfix 3682838).
    • XPS Exporting: Multiple fixes for exporting reports to XPS format.

  5. Understand Microsoft server software support for Azure VMs

    main

    Microsoft supports various server software running in Azure Virtual Machine (IaaS) environments, subject to the Microsoft Support Lifecycle policy.

    Key Licensing and Migration Rules:

    • Licensing: All software installed in an Azure VM must be licensed correctly. Azure VMs typically include a license for Windows Server. Other software licenses must be obtained separately or via the Microsoft License Mobility program.
    • In-place Upgrades: Microsoft does not support in-place operating system upgrades for certain versions in Azure VMs. Instead, you should create a new Azure VM with the required supported OS version and migrate the workload using Windows Server migration tools.
    • Unsupported OS: Operating systems past their End of Support date are not supported without a Custom Support Agreement (CSA).

  6. Best practices for DNS dynamic update troubleshooting

    main

    When troubleshooting DNS dynamic update failures, identify which component is failing to perform the update:

    1. The DNS Client: The client is not sending the update request.
    2. The DHCP Server: The server is intended to update the record on behalf of the client, but the functionality is failing.
    3. The DNS Server: The server receives the request but cannot update the record due to permission issues.

    To prevent these issues, follow Microsoft's standard recommendations regarding client registration, zone security, and server architecture.

  7. What is Inspektor Gadget?

    main

    Inspektor Gadget is a framework for monitoring, troubleshooting, and securing Linux and Kubernetes workloads. It uses Gadgets—tools powered by eBPF programs—to collect low-level kernel data.

    The framework automatically enriches this low-level data with high-level Kubernetes context (such as pod names and namespaces), making it easier to map system events to specific workloads. It supports built-in gadgets for common tasks like tracing process creation, file access, and network activity, but also allows you to run custom eBPF programs via the run command.

  8. Important migration notice for unmanaged NGINX ingress controllers

    main

    The Kubernetes SIG Network and the Security Response Committee have announced the upcoming retirement of the Ingress NGINX project, with maintenance ending in March 2026.

    AKS is moving toward Azure API Gateway as the long-term standard for ingress and L7 traffic management.

    Migration paths for OSS NGINX users:

    • Option 1: Migrate to the application routing add-on with NGINX to receive official support through November 2026 while planning a long-term migration.
    • Option 2: Migrate to the application routing API Gateway implementation for an API Gateway-based experience.
    • Option 3: Migrate to Application Gateway for Containers, which supports both Application Gateway Ingress Controller (AGIC) and API Gateway.

    Service mesh users: If adopting a service mesh, consider the Istio-based service mesh add-on. Use Istio Ingress today and plan to migrate to Istio API Gateway support when available.

  9. Use the $WinpeDriver$ folder for automatic driver injection

    main

    Setup.exe automatically looks for a folder named $WinpeDriver$ on the root of the installation media (e.g., a USB drive). If found, Setup recursively parses this folder for *.INF files and attempts to install them into the driverstore.

    Recommended Folder Structure: Place your drivers in a subfolder structure on the root of your USB device:

    $WinpeDriver$
 └\WiFi
  └\Wireless1
   Wireless.INF
   Wireless.SYS
   Wireless.CAT

    Verification: You can verify if Setup is checking this folder by reviewing \Windows\Panther\Setupact.log. Look for entries starting with PnPIBS: Checking for pre-configured driver paths ....

  10. Understand Application Access Policy (AAP) scoping and ranking

    main

    If an AAP is configured but registrations still fail, the policy might not be applying to the webinar organizer.

    Precedence/Ranking Rules:

    1. Direct per-user assignment (Highest priority)
    2. Group assignment
    3. Global assignment (Lowest priority)

    Key Troubleshooting Concepts:

    • Narrower scope wins: If an organizer is part of a group with a specific policy, that policy overrides the Global policy, even if the Global policy is more permissive. If the group policy is missing permissions, the registration will fail.
    • Group Membership: For group-scoped policies, the organizer must be a member of the group.
    • Single Policy Rule: Only one policy applies to a user. To avoid conflicts, do not split app IDs across multiple policies. Use the -AppIds <ID1>, <ID2> syntax to include all required IDs in a single policy.
    • Propagation Delay: AAP changes can take up to 30 minutes to take effect.
    # Check the rankings of assigned policies
Get-CsGroupPolicyAssignment -PolicyType ApplicationAccessPolicy

  11. Identify if a trigger is Polling or Webhook

    main

    Power Automate uses two trigger types that behave differently when a flow is turned back on:

    • Polling triggers (e.g., recurrence): Periodically check a service for new data. When turned back on, they process all unprocessed or pending events. To avoid processing pending items, delete and re-create the flow.
    • Webhook triggers: Respond to a push of new data. When turned back on, they only process new events generated after the flow is turned on.

    To determine your trigger type, check for a recurrence section with an frequency element in the code view.

    In the New Designer:

    1. In the left configuration pane, select Code View.
    2. Look for a recurrence section containing a frequency element.

    In the Classic Designer:

    1. On the title bar, select the ellipsis (...) > Peek code.
    2. Look for a recurrence section containing a frequency element.
    # Example of a polling trigger structure (conceptual)
{
  "recurrence": {
    "frequency": "Minute",
    "interval": 15
  }
}

  12. Understand Microsoft Dynamics GP support vs. consulting engagement boundaries

    main

    Microsoft support professionals use specific guidelines to determine if a support case qualifies as standard support or must be transitioned to a consulting engagement.

    Key Thresholds:

    • Time Limit: Generally, if an engineer spends more than 30 minutes testing or explaining an issue, it may be classified as a consulting engagement.
    • Complexity: Requests for step-by-step instructions for custom implementations, complex modifications, or multiple functional changes (e.g., more than one table link or one calculated field) are considered consulting.
    • Advisory Requests: Microsoft Dynamics GP Support no longer accepts direct advisory requests. Complex customizations should be handled via a Partner or an Independent Software Vendor (ISV).

    Note on Charges: If an engineer works more than one hour on an issue, the case remains chargeable even if the issue is not resolved.