Cloud Solution Providers (CSP) and enterprises IT organizations that manage resources across multiple tenants struggle while switching tenants, managing vaults and registers with credentials, and repetitive management activities when they do not have access to a centralized view of all their environments in Azure. Microsoft introduced Azure Lighthouse in 2019 to provide a single panel to manage, automate, scale, and improve governance in resources across multiple tenants. The integration of Azure Migrate to Azure Lighthouse has simplified the migration process allowing admins to discover, assess, and migrate workloads at scale while tenant admins still have full visibility and control of their environments.<\/p>\n
Azure Lighthouse helps service providers and enterprises with multiple tenants build and deliver managed services with greater efficiency. Here are some of the advantages of using Azure Lighthouse.<\/p>\n
When Azure Migrate tooling is used in migration projects to discover, assess, and migrate diverse workloads to Azure, the service provider generally has to access each subscription individually through a CSP (Cloud Solution Provider) subscription model or by creating a guest user on the target tenant. Accessing each tenant individually is not only an inefficient method for migrating and managing services but can also pose security risks.<\/p>\n
With Azure Lighthouse, migration engagements are streamlined by leveraging Azure resource delegation to access all relevant Azure Migrate projects across multiple customer tenants and subscriptions using a single view from the managed tenant. Moreover, risks and security exposure can be reduced substantially by following the least privilege access model based on zero-trust security principles with Azure Lighthouse.<\/p>\n
There are two commonly used scenarios for creating an Azure Migrate project with Azure Lighthouse depending upon contracts and migration requirements.<\/p>\n
When migration is performed with Azure Lighthouse by creating an Azure Migrate project in the managing tenant, the resources for the project, such as discovery and assessment data, will remain in the managing tenant. The data can be exported and shared with the serviced tenant. Because actions are initiated from the managing tenant, migration discovery and assessment projects can be done faster as certain steps to be performed in the customer subscriptions and tenants will be reduced.<\/p>\n
In this case, although discovery, assessment, and migration can be initiated from the managing tenant with the customer subscription\/ tenant as the target, resources will not be created or stored in the managing tenant. With this approach, although the customers can keep resources in their own tenants, service providers and enterprises managing multiple tenants will not have to switch contexts frequently.<\/p>\n
While the integration of Azure Migrate into Azure Lighthouse streamlines Azure migrations at scale, most migrations are unique because of the variations in the on-premises infrastructure.<\/p>\n
As a Tier 1 Microsoft CSP, Apps4Rent provides managed Azure services<\/a><\/span> to migrate workloads and control delegated customer resources with advanced tools such as Azure Lighthouse and Microsoft recommended best practices. Email, chat or talk with our Microsoft-certified Azure architects available 24\/7 for assistance.<\/p>\n