Cannot delete Azure Native New Relic Service (ANLRS) monitor - "not eligible" error even with Full Platform Admin user

暢夫 関 0 Reputation points
2026-03-14T03:44:15.64+00:00

Problem

I created an Azure Native New Relic Service (ANLRS) monitor resource (NewRelic.Observability/monitors) via Bicep in my resource group. The resource has provisioningState: Failed.

When I try to delete this resource (via Azure Portal, Azure CLI az resource delete, or REST API), I get the following error:

"your email id is not eligible to delete the current resource. Please contact your organization admin." (Code: BadRequest)

What I have tried

Direct deletion via az resource delete and az new-relic monitor delete — same "not eligible" error

ARM Complete mode deployment with empty template — DeploymentFailedCleanUp error (NR resource provider still blocks deletion)

Different API versions (2024-01-01, 2024-03-01) — same error

Upgraded NR user to Full Platform + Admin group — still "not eligible"

Checked for resource locks — no locks on resource or resource group

Resource move — not supported for NewRelic.Observability/monitors

Tagging/PATCH — NR resource provider rejects all modifications

Resource group force delete — resource group recovered but NR resource remains

Key difference from similar cases

A similar issue was reported in New Relic community topic (aAXPh0000001OGP) where the user's NR organization had been deleted, making the resource undeletable. In my case, the NR organization and account still exist and are accessible. The root cause appears to be the provisioningState: Failed status causing the NR resource provider's eligibility validation to reject all deletion requests regardless of user role.

Environment

Resource type: NewRelic.Observability/monitors

Resource provider: NewRelic.Observability (registered)

provisioningState: Failed

Region: Japan East

Azure subscription type: Pay-As-You-Go

Question

Is there a way to force-delete this stuck ANLRS monitor resource from the Azure side, or does this require escalation to the New Relic resource provider team (Liftr)? Has anyone found a workaround for NewRelic.Observability/monitors resources stuck in provisioningState: Failed that cannot be deleted?

Azure
Azure

A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-03-14T03:44:29.04+00:00

    Force-deleting this stuck Azure Native New Relic Service (ANLRS) monitor resource from the Azure side is not supported in the public tooling or ARM behaviors described in the context. Deletion of NewRelic.Observability/monitors is handled by the New Relic resource provider, and the DeleteAsync operation explicitly requires a valid userEmail and performs provider-side validation.

    The NewRelicMonitorResource.DeleteAsync API:

    • Deletes the monitor resource and stops observability for Azure resources.
    • Requires a non-null userEmail parameter and runs as a long‑running operation.
    • Is implemented by the NewRelic.Observability resource provider, which is where the “not eligible” check is enforced.

    Because:

    • The resource is already in provisioningState: Failed,
    • All delete paths (Portal, CLI, REST, ARM complete mode) are being rejected by the provider with an eligibility error, and
    • There is no ARM/Resource Manager behavior documented that bypasses the provider’s delete logic for this type,

    this scenario requires escalation to the New Relic side rather than an Azure-only workaround.

    The supported path is:

    1. Open a support request with New Relic and provide:
      • Subscription ID, resource group, monitor name, and region.
      • The full error message and correlation IDs from failed delete attempts.
      • Confirmation that the New Relic org/account still exists and that the caller has admin rights.
    2. If needed, also open an Azure support ticket under the Azure Native New Relic Service, so the Azure team can coordinate with the New Relic/Liftr provider team.

    For related behaviors:

    • Diagnostic settings and log forwarding issues for ANLRS are known to require manual cleanup or lock removal, but these do not provide a mechanism to bypass provider-side delete eligibility checks.
    • Resource locks can prevent cleanup of diagnostic settings, but in this case locks are already ruled out.

    There is no documented Azure-side “force delete” that skips the New Relic provider for NewRelic.Observability/monitors, so resolution depends on New Relic/Liftr support correcting the provider state or performing a backend delete.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.