veeam backup for office 365 best practices

Regardless of the resiliency and uptime of cloud SaaS environments, having this standalone copy of your data stored outside Microsoft 365 is essential to best practice methodologies. The 3-2-1 model dictates that you have (3) copies of your data stored on at least (2) forms of media, with at least (1) copy stored offsite. In light of the 3-2-1 backup model, a long-held industry best practice model for data backups, getting copies of your data 'out' of your production environment is critical. Microsoft shared responsibility model for SaaS environments As a result, the information in the shared responsibility model should be an eye-opener for business leaders, including CIOs, CISOs, and IT admins. It indicates that your information and data are your responsibility, not Microsoft's.Īs expected, for SaaS environments, Microsoft is responsible for the underlying applications, network controls, operating systems, physical hosts, networks, and the physical data center. The first item listed under Responsibility is Information and data. In the following infographic, Microsoft defines the burden of responsibilities between SaaS, PaaS, IaaS, and on-premises environments. Shared responsibility in the cloud-Microsoft Azure | Microsoft Learn.The following link, entitled 'Shared responsibility in the cloud,' defines the division of responsibility between your organization and Microsoft across the different tiers of cloud services. Microsoft provides clear direction on the burden of responsibility for protecting data. Shared responsibility modelĬloud providers, including Microsoft, follow what is known as the 'shared responsibility model.' Amazon, Google, and Microsoft have their own versions of this responsibility model, which provides the basis for understanding the need for proper enterprise backups for your cloud SaaS data. However, the need for backups becomes evident when we consider the 'shared responsibility model' that Microsoft and most cloud providers follow.

Veeam backup for office 365 best practices