Aura Support in Lightning Out 2.0 (Generally Available)

Embed existing Aura components securely on external sites without loading the Aura runtime on the host page. Your components run in a sandboxed iframe with full security isolation, so host-page scripts can't access Salesforce session data. Aura interop is generally available for existing Lightning Out (Beta) customers who complete the Lightning Adoption Program (LAP) enablement process on a case-by-case basis.

Where: This change applies to Lightning Experience in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

Note Aura support in Lightning Out 2.0 is available only to existing Lightning Out (Beta) customers and is enabled through the LAP gate framework on a case-by-case basis. Aura interop isn't available for new customers. Use Lightning web components (LWC) for all new development. Salesforce is investing in LWC as the standard component model, and support for the Aura framework will continue to decrease over time.

Who: To use Aura interop, your org needs the AuraLightningOutPermission permission, granted through the Lightning Adoption Program, and the AuraLightningOutAccess preference enabled in Setup. A Salesforce admin submits the LAP request for AuraLightningOutPermission. After Salesforce grants the permission, users with Setup access open Aura Support Settings and enable AuraLightningOutAccess. Keep the LAP case ID with your change record for support purposes.

How: Register Aura components in your Lightning Out 2.0 app, use the Lightning Out 2.0 bundle and frontdoor-based authentication on the host page, and load components through the Lightning Out 2.0 flow. Mirror attributes and events on the aura-interop host element, not on the inner Aura root. For complete setup instructions, see Set Up Aura Components for Lightning Out 2.0. The Aura Lightning Out 2.0 path automatically bundles Salesforce Lightning Design System (SLDS) styles inside the iframe. Avoid loading a separate copy of SLDS on the host page.