迁移Azure资源的优点和缺点 [英] Migrate Azure Resources Pros and Cons

问题描述

您好，我目前正致力于A公司的解决方案，该解决方案利用Office 365（SharePoint）和Azure（特别是资源Web应用程序，Web作业，Redis缓存和SQL Server）。公司A刚被B公司收购，公司B拥有自己的Office 365和
Azure租户。

Hi, I'm currently working on a solution at Company A which leverages Office 365 (SharePoint) and Azure (specifically with resources Web Apps, Web Jobs, Redis Cache and SQL Server). Company A just got acquired by Company B which has their own Office 365 and Azure tenant.

对于O365，计划是将所有SharePoint站点从A公司的O365迁移到公司B的O365。

For O365, the plan is to migrate all SharePoint sites from Company A's O365 to Company B's O365.

对于Azure，计划是保留两个Azure租户。

For Azure, the plan is to keep both Azure tenants.

保留A公司资源的利弊是什么Azure而不是将资源迁移到公司B的Azure？

What are the pros and cons to keeping the resources in Company A's Azure rather than migrating the resources to Company B's Azure?

推荐答案

这取决于您是否要迁移数据。一些选项是;

It really depends if you want to migrate the data. Some of the options are;

- 如果您不想管理多个sharepoint实例（安全/成本/合规性等），请迁移数据。

- Migrate the data if you do not want to manage multiple sharepoint instances (security/cost/compliance/etc.)

- 如果公司A的sharepoint实例符合新母公司的合规/安全标准，则迁移数据？您可以将公司A的共享点纳入合规性，但是这涉及成本/工作，您必须管理/审计未来的
。

- Migrate the data if Company A's sharepoint instance adhere to the compliance/security standards of new parent company? You could bring Company A's sharepoint to compliance but there are costs/efforts involved in this and you'd have to manage/audit both going forward.

- 迁移数据，如果您希望新员工拥有单个帐户来访问所有sharepoint数据吗？ （从技术上讲，您可以在租户A中为租户B帐户配置访客帐户，但使用访客帐户重建安全分配是一个可能不想打开的可以花费b $ b的蠕虫。

- Migrate the data if you want to have single accounts for new employees to access all sharepoint data? (Technically you can provision guest accounts for Tenant B accounts in Tenant A, but rebuilding the security assignments using guest accounts is a can of worms you probably don't want to open).

- 您的迁移策略是否会导致可能丢失历史记录/元数据/文件所有权信息？如果 是 - 确定这是否是交易破坏者，如果此类数据丢失不可接受（例如出于法律目的），则不迁移数据。如果您最终进入这个
方案，则保留所有正在进行的项目的当前租户并在新租户中提供新项目。共存需要传达给利益相关者，并且会成为一段时间的成本和成本驱动因素。

- Does your migration strategy result in potentially losing history/metadata/file ownership info ? If  yes - determine if that's a deal breaker and don't migrate the data if such data loss not acceptable (eg for legal purposes). If you end up in this scenario then remain in the current tenant for all ongoing projects and provision new projects in the new tenant. The coexistence needs to be communicated to stakeholders and will be a pinpoint and driver of cost for a while.

- 租户A的共享点上是否存在非常自定义的东西（需要大量工作/ reforctoring ot获取Tenant B的sharepoint）并且有关键的可交付成果/项目/客户合同依赖于它保持完整？如果是这样 - 请不要迁移
数据。

- Is there something on Tenant A's sharepoint that is very custom (requires lots of work/refarctoring ot get in Tenant B's sharepoint) and there are key deliverables/projects/client contracts that depend on it remaining intact ? If so - do not migrate the data.

还有很多场景可以评估，因为很多场景会影响迁移VS成本/工作量共存。 

There are many more scenarios you could should evaluate as a lot of it would come down to impact of migration VS the cost/effort of coexistence. 

这篇关于迁移Azure资源的优点和缺点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！