preview
We're still working on this feature, but we'd love for you to try it out!
This feature is currently provided as part of a preview program pursuant to our pre-release policies.
Learn how to set up and configure Autopilot for your organization, including prerequisites, permissions, and alert integration.
Prerequisites
Before setting up Autopilot, ensure you meet the following requirements:
Admin permissions (for setup)
To give users permission to use Autopilot, a user must be an Organization Manager and Authentication Domain Manager.
Tip
If you don't have these permissions, you'll see the message: "This looks like a job for an admin." Contact your organization manager to enable the agent for you.
User permissions (for access)
To use Autopilot, users must be full or core users.
To give users permission to use Autopilot, an admin or authentication domain manager must assign users a role that includes these organization-level capabilities:
- Autopilot - Read, other (Ask, Add to Automation)
- New Relic MCP Server - Read
Preview opt ins
To access Autopilot, you must opt into the following public preview trials:
- Autopilot
- MCP Server
- Cross account destinations
Tip
Cross account destinations is only required if you want to set up alerts with Autopilot. Without this preview, Autopilot will remain partially configured.
Set up Autopilot
Use the onboarding flow to automatically set up:
- A system identity to represent the agent
- Required permissions for basic use
- An alert destination
Important
What is a system identity? A system identity is a non-human identity that allows the agent to authenticate directly to other services without requiring a user account. System identities are scoped to a single New Relic organization.
To onboard Autopilot:
Go to one.newrelic.com
In the upper right, select Ask AI, then select the Configure tab (gear icon).
Under Agents, select Autopilot.
In the Agent name field, enter a name for your agent. The system automatically adds
Autopilot -as a prefix and applies this name to the system identity and access management components.From the dropdown, select the accounts you want the agent to analyze.
Important
Adding more accounts allows the agent to better identify connections and surface insights across your stack. However, the agent's analysis will be visible to any users with Autopilot interaction access, regardless of their direct access to those accounts.
Review the Permissions summary. The system grants Autopilot standard read-only access to your selected accounts.
Important
Admin users will have the ability to modify the accounts and grants provided to the agent. A reduction in grants from the standard read-only role will limit the telemetry data Autopilot can access, which can result in incomplete analysis, missed anomalies, or degraded root-cause identification capabilities.
Click Add Agent. The system takes a few moments to complete the setup.
Tip
Creating the alert destination does not automatically assign any alert conditions or policies to Autopilot. See Integrate with alerts to configure that.
Integrate with alerts
Connect Autopilot to your alert workflows so that Autopilot insights are automatically attached to every fired alert or issue.
Configure alert workflows
Tip
Phased approach recommendation: Start with a small subset of alert conditions or policies to validate performance, confirm the agent works well for your environment, then expand more broadly.
To set up Autopilot with alerts:
- Go to one.newrelic.com > All capabilities > Alerts > Issues & Activity > Notification Workflows > Add a workflow.
- In your workflow configuration, under the Notify section, select AI agent.
- Choose the Autopilot destination created during onboarding and click Save message.
Once configured, when you open a recently fired alert or issue, you'll automatically see the Autopilot summary for that item.