You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Azure Native New Relic Service frequently asked questions
4
+
description: Answers to common questions about using Azure Native New Relic Service
5
+
ms.topic: faq
6
+
ms.date: 12/17/2025
7
+
8
+
title: Azure Native New Relic Service FAQ
9
+
summary: |
10
+
Find answers to common questions about Azure Native New Relic Service, including setup, management, and billing.
11
+
12
+
sections:
13
+
- name: General
14
+
questions:
15
+
- question: What is Azure Native New Relic Service?
16
+
answer: |
17
+
Azure Native New Relic Service is a fully integrated observability platform developed and managed jointly by Microsoft and New Relic. It provides a single source of truth for application performance, infrastructure monitoring, log management, error tracking, and real-user monitoring. The service is available through Azure Marketplace and the Azure portal, enabling you to monitor and optimize your Azure services and applications.
18
+
- question: What are the main capabilities of Azure Native New Relic Service?
19
+
answer: |
20
+
Azure Native New Relic Service provides the following capabilities:
21
+
22
+
- Seamless onboarding and native integration with Azure
23
+
- Unified billing for all Azure resources and New Relic consumption
24
+
- Automatic monitoring of platform metrics, subscription activity logs, and resource logs
25
+
- Single experience to install and uninstall the New Relic agent on virtual machines and app services
26
+
- Monitoring across multiple Azure subscriptions through a single New Relic resource
27
+
- question: Where can I find Azure Native New Relic Service?
28
+
answer: |
29
+
You can find Azure Native New Relic Service in the [Azure portal](https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/NewRelic.Observability%2Fmonitors) or [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/newrelicinc1635200720692.newrelic_liftr_payg?tab=Overview).
30
+
31
+
- name: Getting started
32
+
questions:
33
+
- question: What are the prerequisites for creating an Azure Native New Relic Service resource?
34
+
answer: |
35
+
To create an Azure Native New Relic Service resource, you need:
36
+
37
+
- An active Azure subscription with owner or contributor access
38
+
- A New Relic subscription (you can subscribe from the Azure portal during resource creation)
39
+
- The `NewRelic.Observability` resource provider registered in your Azure subscription
40
+
- question: How do I register the NewRelic.Observability resource provider?
41
+
answer: |
42
+
To register the resource provider using the Azure portal, follow the guidance in [Azure resource providers and types](/azure/azure-resource-manager/management/resource-providers-and-types).
43
+
44
+
Alternatively, you can register it from the command line by running: `az provider register --namespace NewRelic.Observability --subscription <subscription-id>`
45
+
- question: Can I link an existing New Relic resource to Azure?
46
+
answer: |
47
+
Yes. If you already created New Relic resources outside of Azure, you can link them to your Azure subscription. During resource creation, select the **Create** button under *Link an existing New Relic resource* to associate existing New Relic accounts with your Azure Native New Relic Service resource.
48
+
49
+
- name: Billing and subscription
50
+
questions:
51
+
- question: How is Azure Native New Relic Service billed?
52
+
answer: |
53
+
When using Azure Native New Relic Service, you receive a single bill for all resources you consume on Azure, including New Relic. An Azure Marketplace SaaS resource is created automatically based on the plan you select during resource creation. This resource is used for billing purposes.
54
+
55
+
Note: If you created your New Relic organization directly from the New Relic portal, the Azure Marketplace SaaS resource doesn't exist, and New Relic manages your billing separately.
56
+
- question: What billing plans are available?
57
+
answer: |
58
+
Azure Native New Relic Service offers multiple billing plans that you can select during resource creation. You can change your billing plan after creation by selecting the **Change plan** link in the resource management portal.
59
+
- question: Do I need to subscribe to New Relic separately?
60
+
answer: |
61
+
You must have a New Relic subscription to use Azure Native New Relic Service. You can subscribe directly from the Azure portal during the resource creation process, or subscribe beforehand through the Azure Marketplace.
62
+
- question: What happens if my Azure subscription is suspended or deleted?
63
+
answer: |
64
+
If your Azure subscription is suspended or deleted due to payment-related issues, resource monitoring in New Relic automatically stops. To resume monitoring, use a different Azure subscription or add or update your payment method. For more information, see [Add, update, or delete a payment method](/azure/cost-management-billing/manage/change-credit-card).
65
+
66
+
- name: Creation and configuration
67
+
questions:
68
+
- question: What settings do I configure when creating a New Relic resource?
69
+
answer: |
70
+
When creating an Azure Native New Relic Service resource, you configure:
71
+
72
+
- **Project details**: Select your Azure subscription and resource group
73
+
- **Azure resource details**: Specify a unique resource name and select a deployment region
74
+
- **New Relic account details**: Create a new organization or associate with an existing one, and select a billing plan
75
+
- **Metrics and logs** (optional): Configure monitoring of platform metrics, subscription activity logs, and Azure resource logs
76
+
- **Tags** (optional): Add tags to organize your resource
77
+
- question: Can I configure metrics and logs collection?
78
+
answer: |
79
+
Yes. After creating your New Relic resource, you can configure metrics and logs collection:
80
+
81
+
- **Enable metrics collection** to set up monitoring of platform metrics
82
+
- **Subscription activity logs** to send subscription-level logs to New Relic
83
+
- **Azure resource logs** to send Azure resource logs to New Relic
84
+
85
+
You can also collect metrics for virtual machines and app services by installing the New Relic agent after creating the resource.
86
+
- question: Can I change my New Relic organization after creation?
87
+
answer: |
88
+
No. When you associate your Azure Native New Relic Service resource with a New Relic organization, that resource is billed to that organization's plan. If you need to change organizations, you may need to create a new resource.
89
+
90
+
- name: Management and monitoring
91
+
questions:
92
+
- question: How do I manage my New Relic resource?
93
+
answer: |
94
+
You can manage your Azure Native New Relic Service resource from the Azure portal. Access the resource overview to view essentials like resource group, region, subscription, tags, and billing information. You can also navigate to specific tabs for:
95
+
96
+
- **Get started**: Quick links to New Relic dashboards, logs, and alerts
97
+
- **Monitoring**: Summary of resources sending logs and metrics to New Relic
98
+
- question: Can I monitor multiple Azure subscriptions with a single New Relic resource?
99
+
answer: |
100
+
Yes. You can monitor all your subscriptions through a single New Relic resource using the **Monitored Subscriptions** feature. Instead of creating a New Relic resource in every subscription, link multiple subscriptions to a single New Relic resource tied to a New Relic organization.
101
+
- question: How do I add more subscriptions to monitor?
102
+
answer: |
103
+
To add subscriptions for monitoring:
104
+
105
+
1. Select **New Relic account config** > **Monitored Subscriptions** from the service menu
106
+
2. Select **Add subscriptions**
107
+
3. Select the subscriptions you want to monitor
108
+
4. Select the **Add** button
109
+
110
+
The tag rules and logs you defined for the New Relic resource apply to all selected subscriptions.
111
+
- question: What should I do if I see duplicate data across subscriptions?
112
+
answer: |
113
+
If you have existing New Relic resources linked to the same New Relic organization, duplicate logs can result in unnecessary charges. To prevent this, delete redundant New Relic resources that are already linked to the account. We recommend consolidating subscriptions into the same New Relic resource where possible.
114
+
- question: Can I reconfigure metrics and logs rules after creation?
115
+
answer: |
116
+
Yes. To change the configuration rules for metrics and logs, select **New Relic account config** > **Metrics and logs** from the service menu. Note that it takes up to one hour for modifications to tag rules to reflect in the log flow.
117
+
- question: How do I view which resources are sending data to New Relic?
118
+
answer: |
119
+
To see the list of resources sending metrics and logs to New Relic, select **New Relic account config** > **Monitored resources** from the service menu. You can filter by resource type, resource group name, region, and whether the resource is sending metrics and logs.
120
+
121
+
- name: Agents and extensions
122
+
questions:
123
+
- question: Which resources can I monitor with the New Relic agent?
124
+
answer: |
125
+
You can install and manage the New Relic agent on:
126
+
127
+
- Virtual machines
128
+
- Virtual Machine Scale Sets
129
+
- App Services (Windows-based only; Linux App Services aren't supported)
130
+
131
+
Note: Function Apps aren't supported at this time.
132
+
- question: How do I install the New Relic agent?
133
+
answer: |
134
+
To install the New Relic agent:
135
+
136
+
1. Navigate to **New Relic account config** and select the resource type (**Virtual Machines**, **Virtual Machine Scale Sets**, or **App Services**)
137
+
2. Select the resources where you want to install the agent
138
+
3. Select **Install Extension** from the command bar
139
+
140
+
Note: The agent can only be installed on running resources. Stopped virtual machines can't have the agent installed.
141
+
- question: Why can't I install an agent on my virtual machine?
142
+
answer: |
143
+
The New Relic agent can only be installed on virtual machines that are currently running. If your virtual machine is stopped, the install option will be disabled. Start the virtual machine first, then install the agent.
144
+
- question: Can I uninstall the New Relic agent?
145
+
answer: |
146
+
Yes. You can uninstall the New Relic agent extension by selecting resources that have the agent installed and selecting **Uninstall Extension** from the command bar. Note that only resources with the agent currently installed can be selected for uninstallation.
147
+
- question: What does "Agent status: Partially Installed" mean for Virtual Machine Scale Sets?
148
+
answer: |
149
+
This status appears when you have Virtual Machine Scale Sets with manual upgrade policy where preexisting instances didn't receive the extension automatically. To resolve this, manually install the New Relic agent for each preexisting virtual machine.
150
+
- question: What is the difference between Web Apps and Function Apps?
151
+
answer: |
152
+
Azure Native New Relic Service supports Web App Services only. Function Apps aren't supported at this time. Additionally, extensions are only supported for App Services running on Windows operating systems; Linux App Services aren't displayed.
153
+
154
+
- name: Troubleshooting
155
+
questions:
156
+
- question: Why aren't logs being sent to New Relic?
157
+
answer: |
158
+
Only resource types in [supported categories](/azure/azure-monitor/essentials/resource-logs-categories) send logs to New Relic through the integration. To verify setup, go to the [Azure diagnostic settings](/azure/azure-monitor/platform/diagnostic-settings) for that resource and confirm a New Relic diagnostic setting exists.
159
+
- question: What should I do if resource monitoring stopped working?
160
+
answer: |
161
+
Resource monitoring is enabled through the ingest API key created during resource setup. If monitoring stopped:
162
+
163
+
- Check that the ingest API key hasn't been revoked from the New Relic portal (revoking it disrupts all monitoring)
164
+
- Verify your Azure subscription is active and not suspended due to payment issues
165
+
- Contact New Relic support if the issue persists
166
+
- question: Why are diagnostic settings still active after I disabled the New Relic resource?
167
+
answer: |
168
+
If diagnostic settings remain active after disabling the New Relic resource or applying tag rules, a delete lock may be applied to the resources or resource group. Delete locks prevent cleanup of diagnostic settings. Remove the lock from the resource or resource group to allow cleanup. If the lock is removed after the resource is deleted, you'll need to manually clean up the diagnostic settings to stop log forwarding.
169
+
- question: Why are logs still being forwarded after I deleted the New Relic resource?
170
+
answer: |
171
+
If logs continue after deletion, a resource lock may be present on monitored Azure resources. Log forwarding will stop after 24 hours for locked resources. To stop forwarding immediately, remove the resource locks.
172
+
- question: How long does it take for tag rule changes to take effect?
173
+
answer: |
174
+
It takes up to one hour for any modifications to tag rules to reflect in the log flow. For example, if you add a new resource to tag rules, it would take about one hour for log forwarding to start for that resource.
175
+
- question: How do I get support for Azure Native New Relic Service?
- Request support in the Azure portal: Select **Support + Troubleshooting** from the service menu, then choose the link to [log a support request in the New Relic portal](https://support.newrelic.com/)
181
+
182
+
additionalContent: |
183
+
## Related content
184
+
185
+
- [Quickstart: Get started with Azure Native New Relic Service](create.md)
186
+
- [Manage Azure Native New Relic Service](manage.md)
187
+
- [Azure Native New Relic Service overview](overview.md)
188
+
- [Troubleshoot Azure Native New Relic Service](troubleshoot.md)
0 commit comments