Microsoft Office Tutorials and References
In Depth Information
Summary
It is important to note that it does not mean the organization becomes compliant with the
standards just by adopting Office 365; instead, it means that the organization can maintain
or achieve the regulatory compliance with Office 365 as part of their portfolio. It is
necessary to make this distinction because portions of the standards might cover requirements
that are not part of Office 365. For example, a particular requirement might dictate that
records are kept for only 365 days, after which they must be destroyed. This is an
organization process. Office 365 meets this requirement because it provides the tools and methods
that can easily implement this requirement. However, it might be up to the organization
to actually create a policy and process and configure Office 365 services to adhere to the
requirement.
Note
You can find detailed information about regulatory compliance at http://www.microsoft.
com/online/legal/v2/?docid=31 .
Summary
This chapter discussed the core principles upon which Office 365 is built: privacy,
transparency, security, and compliance. The core principles and economic relevance of Office 365
have made the cloud a significant and permanent part of any organization's IT portfolio.
The following chapters will dive into the technical details and lessons learned by
organizations that have adopted Office 365 since its debut as the Business Productivity Online
Services (BPOS).
Search JabSto ::




Custom Search