AMA Removal Tool Documentation Fixes

[gkgab-ptr]

The link can be found here: https://learn.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-mma-removal-tool?tabs=single-tenant%2Cdiscovery

Prerequisites: The resource group, UAI and the corresponding permissions are created by the script and not necessarily a prereq

Set up the utility: 1. The script is MMARemovalUtilityConsolidatedSetup.ps1 not MMARemovalUtilitySetupConsolidated.ps1

Set up the utility: 3. Bicep deployment consistently fails with Bad requests at MMARemovalenvironmentsetup at the steps MMARemovalUtility-ScopeResolver-3ee3d/MSDeploy, MMARemovalUtility-ExtensionRemovalStatusCheck-3ee3d/MSDeploy and MMARemovalUtility-ScopeResolverTrigger-3ee3d/MSDeploy with failure in the deployment template: "Code 429: Cannot acquire exclusive lock to create or update this server farm. Retry the request later." - Bicep CLI version used: 0.25.3

Set up the utility: 3. Location property seems to be required - not sure about the domain controller reference in the description?

Run the utility: "Update-AzTSMMARemovalUtilityDiscoveryTrigger" cannot be found, presumably because of the failures at setting up the utility.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: b6492b16-82f3-73da-99bf-471277fbd74b
• Version Independent ID: 7e5fbd8f-4699-c65a-e147-5ed5564db19f
• Content: MMA Discovery and Removal Utility - Azure Monitor
• Content Source: articles/azure-monitor/agents/azure-monitor-agent-mma-removal-tool.md
• Service: azure-monitor
• Sub-service: agents
• GitHub Login: @guywi-ms
• Microsoft Alias: guywild

[AjayBathini-MSFT]

@gkgab-ptr Thanks for your feedback! We will investigate and update as appropriate.

[MonikaReddy-MSFT]

@gkgab-ptr - - Thanks for bringing this to our attention. I'm going to assign this to the document author so they can review and update accordingly.

[ArjunRajan52]

@MonikaReddy-MSFT , Is there any update on this? I'm still having the following error

Update-AzTSMMARemovalUtilityDiscoveryTrigger: The term 'Update-AzTSMMARemovalUtilityDiscoveryTrigger' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

[guywi-ms]

@JeffreyWolford please advise.

[JeffreyWolford]

There was an issue in the script that has been fixed. Please can you please downloaded latest zip package from here

https://github.com/azsk/AzTS-docs/blob/main/TemplateFiles/AzTSMMARemovalUtilityDeploymentFiles.zip

[ArjunRajan52]

Hello,

I managed to complete all the steps for discovery and removal, and I don't see any errors. However, none of the shared dashboard widgets are updating except for "Progress: Configured scopes triggered for discovery phase." Additionally, I don't see the MMA removed for the scope that I set.

PowerShell results for Removal :

================================================================================ Configuring MMA Removal utility removal phase trigger...

Updating extension removal scheduler configurations... Checking if WorkItemScheduler function app [MMARemovalUtility-WorkItemScheduler-4de94] exists... WorkItemScheduler function app [MMARemovalUtility-WorkItemScheduler-4de94] exists. MMA 'Removal' phase has been enabled. Successfully Updated extension removal scheduler configurations.

Completed MMA Removal utility removal phase trigger.

I am happy to share the details in private.

[ArjunRajan52]

Hello All,

Is there any update on my issue?

[JeffreyWolford]

Please share the details with me, so we can triage the problems.

[ArjunRajan52]

Hello,

As I shared it in my previous email, I have done all the steps suggested in the documentation However, It's not removing or the dashboard not getting updated. Please let me know what details you require?

Best Regards, Arjun Rajan Selvaraj

On Fri, Apr 5, 2024 at 5:17 AM Jeffrey Wolford @.***> wrote:

Please share the details with me, so we can triage the problems.

— Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/azure-docs/issues/119980#issuecomment-2038239109, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOMGGEI443K4AMGAPG2DGI3Y3W7NHAVCNFSM6AAAAABDPH6TNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZYGIZTSMJQHE . You are receiving this because you commented.Message ID: @.***>

[usernamefreek]

Hi, the issue still occured to us. The function is in the MMARemovalUtilitySetup.ps1 file, but in step 1 you only load the MMARemovalUtilityConsolidatedSetup.ps1 file. If you enter this commmand: . .\MMARemovalUtilitySetup.ps1 and then run the update-AzTSMMARemovalUtilityDiscoveryTrigger command it should work.

[droz36]

Having same issue!!!!

[lecthomp]

.\MMARemovalUtilitySetup.ps1 and then run the update-AzTSMMARemovalUtilityDiscoveryTrigger command it doesn't work.

$ExecutionContext.SessionState.LanguageMode FullLanguage

Bicep --version Bicep CLI version 0.26.54 (5e20b29b58)

$PSVersionTable

Name Value

---

PSVersion 5.1.26100.268 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.26100.268 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1

Same results when follow the instruction online "term not recognized"