[Feature]: PowerShell defaulting the MSI support for Enable-AzAksAddOn Monitoring

### Description of the new feature

Hi @Alex @Teresa

Bumping and following up the thread, please share us know the work item for defaulting the MSI support for Enable-AzAksAddOn Monitoring. And also the estimated schedule for merging the AzPS logic with the AzCLI path. Meanwhile let us know if you need things from our side, thank you!

Bests,

Long

From: Teresa Ritorto
Sent: Monday, March 2, 2026 6:27 PM
To: LONG WAN ; Alex Wang ; Michael Greene (POWERSHELL)
Cc: Vidhi Mehta ; Joby Thomas ; Rashmi Chandrashekar ; Container Insights - Logs ; azure-ct-obs-squad
Subject: Re: PowerShell Enable-AzAksAddOn Monitoring Deprecation request (legacy monitoring mode)

+ @azure-ct-obs-squad - fyi


Teresa Ritorto

Principal Software Eng Lead
tritorto@microsoft.com

Microsoft Logo

From: LONG WAN
Sent: Tuesday, March 3, 2026 4:25 AM
To: Alex Wang ; Michael Greene (POWERSHELL)
Cc: Vincent Dai ; Vidhi Mehta ; Joby Thomas ; Rashmi Chandrashekar ; Container Insights - Logs ; Yeming Liu ; Teresa Ritorto ; Yu Chen
Subject: RE: PowerShell Enable-AzAksAddOn Monitoring Deprecation request (legacy monitoring mode)

Hi @Alex,

Thanks for the clarification about maintaining a consistent onboarding experience between Az PowerShell and Azure CLI, given the number of AKS customers who rely on PowerShell.

As a concrete next step, for Enable-AzAksAddOn to work with the latest agent, AzPS should set the following in the omsagent addon profile: "useAADAuth": "true" azure-powershell/src/Aks/Aks/Utils/AddonUtils.cs at main ? Azure/azure-powershell. Could you please plan to have Az PowerShell set this flag in the omsagent addon profile by default?

Also, if the plan is to merge/sync the AzPS logic with the AzCLI path going forward (so we don’t introduce additional net-new maintenance), that works well for us.

Could you please share the expected schedule / rollout plan for the AzPS updates (or loop us in when it’s ready)? Once we have the timeline and confirmed behavior, we can update our public documentation and guidance accordingly.

Thanks,
Long

From: Alex Wang
Sent: Thursday, February 26, 2026 1:24 PM
To: LONG WAN ; Michael Greene (POWERSHELL)
Cc: Vincent Dai ; Vidhi Mehta ; Joby Thomas ; Rashmi Chandrashekar ; Container Insights - Logs ; Yeming Liu ; Teresa Ritorto ; Yu Chen
Subject: Re: PowerShell Enable-AzAksAddOn Monitoring Deprecation request (legacy monitoring mode)

hi @LONG WAN,

However, this is incorrect. We have a large number of AKS users who also use Azure PowerShell, and this would significantly degrade the user experience for this part.

I recommend maintaining the same experience for Azure PowerShell and the CLI. I know that maintaining PowerShell is currently quite challenging, and we are planning to address the consistency issues between Azure CLI and AzPS in our future planning. In that case, the maintenance workload will be merged with AzCLI, without adding any new maintenance work.

Regards

Alex Wang

From: LONG WAN
Sent: Thursday, February 26, 2026 10:33 AM
To: Alex Wang ; Michael Greene (POWERSHELL)
Cc: Vincent Dai ; Vidhi Mehta ; Joby Thomas ; Rashmi Chandrashekar ; Container Insights - Logs ; Yeming Liu ; Teresa Ritorto ; Yu Chen
Subject: RE: PowerShell Enable-AzAksAddOn Monitoring Deprecation request (legacy monitoring mode)

Hi @Alex Wang the Enable-AzAksAddOn for monitoring can support our latest agent with "useAADAuth": "true" in omsagent addon profile. But we’re planning to deprecate PowerShell onboarding for azure monitoring logs because it adds ongoing maintenance cost. Also, our public docs don’t include PowerShell as a supported onboarding method for azure monitoring logs or metrics.

For customers, we’ll direct them to the supported onboarding paths (Azure CLI, Portal, ARM, Terraform) and share the latest recommended commands/docs as part of the deprecation update for legacy mode.

Thanks,

Long

From: Alex Wang
Sent: Wednesday, February 25, 2026 5:11 PM
To: LONG WAN ; Michael Greene (POWERSHELL)
Cc: Vincent Dai ; Vidhi Mehta ; Joby Thomas ; Rashmi Chandrashekar ; Container Insights - Logs ; Yeming Liu ; Teresa Ritorto ; Yu Chen
Subject: Re: PowerShell Enable-AzAksAddOn Monitoring Deprecation request (legacy monitoring mode)

hi @LONG WAN,

Thanks for reaching out to us.

After enabling-AzAksAddOn deprecate,

Is there an updated monitor API? Should we provide users with the latest monitor command line?

Regards

Alex Wang

From: LONG WAN
Sent: Thursday, February 19, 2026 9:45 AM
To: Alex Wang ; Michael Greene (POWERSHELL)
Cc: Vincent Dai ; Vidhi Mehta ; Joby Thomas ; Rashmi Chandrashekar ; Container Insights - Logs
Subject: PowerShell Enable-AzAksAddOn Monitoring Deprecation request (legacy monitoring mode)

Hi @Alex Wang @Michael Greene,

I’m reaching out from the Azure Monitoring (Logs & Metrics) team. We’d like to request deprecating PowerShell enablement of AKS monitoring via `Enable-AzAksAddOn` (Az.Aks) / Enable-AzAksAddOn (Az.Aks) | Microsoft Learn, specifically the Monitoring add-on path, because it enables monitoring through the legacy (OMS/omsagent) mode which we announced deprecation.

This legacy enablement path is a source of customer issue and confusion if customer onboard through PowerShell. Retiring this path would reduce support burden, keep alignment, and prevent new clusters from being onboarded into a mode that is no longer the recommended/default direction.

For reference, the monitoring-related implementation in Azure PowerShell appears here: https://github.com/Azure/azure-powershell/blob/main/src/Aks/Aks/Utils/AddonUtils.cs. Please let us know the preferred process and requirements on the Az PowerShell side to evaluate and drive this deprecation (including any policy, compatibility, or documentation considerations).

Thanks,

Long

Azure Monito

### Proposed implementation details (optional)

_No response_