With Microsoft, you’re the owner of your own customer information. We use your customer information simply to offer the services we’ve agreed upon, and also for purposes which are compatible with supplying those services. We don’t share your information with our advertiser-supported services, nor do we mine for advertising or advertising. And if you depart our services, we consider the necessary steps to ensure your continuing ownership of your information.
WB just purchased Office 365, and they’re thinking about using Exchange Online, SharePoint Online, and Skype for Business. They will first configure a hybrid vehicle configuration for Exchange Online and will migrate Exchange mailboxes first. Afterward they’ll upload their record libraries into SharePoint Online.
WB begins their cloud migration by choosing the appropriate network setup for their own organization. This is actually the first time that customer information is touched by almost any Microsoft cloud service (specifically, in this point WB can optionally synchronize their inner Active Directory using Azure Active Directory).
WB has chosen to migrate the information using the internet mailbox transfer process. The Exchange data migration is started by running the Online Transfer Mailbox Wizard. The mailbox transfer process is as follows:
MRS asynchronously transfers the mailbox information via HTTPS to some customer access front-end (CAFÉ) server at Office 365.
The CAFÉ server transfers the information via HTTPS to the Store Driver onto a Mailbox server at a database availability group in the appropriate datacenter.
As with all Exchange Online servers, the transferred mail info is stored in a mailbox database that is hosted on a BitLocker-encrypted storage quantity. Had WB opted to get a PST migration, the information could have also been encoded before ingestion.
Throughout the mail information transfer and upon conclusion, an audit trail of the mailbox is stored on servers in either the source on-premises Exchange business and on servers in Office 365. MRS will also create a record of the mailbox transfer and its statistics.
After WB’s information is stored in a mailbox in Exchange Online, then it is going to be reproduced and resized and sitting at rest in an encrypted state, together with access management limited to the designated user and also anybody else given permission by WB’s administrator.
The process starts by producing a couple of sites from SharePoint Online to maintain the documents. All customer communication with SharePoint Online is performed via HTTP secured with TLS. After uploading a couple of documents to SharePoint Online, the documents are transmitted using standard HTTP PUT using TLS 1.2 encryption used between the customer and SharePoint Online server. When the record has been obtained by the SharePoint Online server, it is stored in an encrypted state. The file is then duplicated to another local server and also to distant servers, in which it is also stored in an encrypted state.
The process begins by opening the OneDrive for Business folder to the customer and copying the files to the folder. After the files are copied, a synchronization process copies the information to the user’s cloud-based One Drive for Business folder.
The documents are then copied to another local server and also to distant servers, where they’re also stored in an encrypted state.
At this point, WB has on-boarded to Exchange Online and SharePoint Online, and now wish to start using Skype for Business for internet meetings along with other features. Occasionally, meeting participants may upload files into the meeting for sharing. When a document is uploaded to Skype for Business, it is transferred by the customer to the Skype for Business server using encrypted communications. When the record has been uploaded into the Skype for Business server, it is stored in an encrypted state.
As a part of our continuing transparency efforts, and also to help you fully understand the way your information is processed and shielded from Office 365, we’ve published a listing of whitepapers that describe various architectural and architectural aspects of our service. These whitepapers, along with other articles, are adapting to things we do with customer information.
Every one of the above links will take you to articles in our Office 365 risk assurance documentation library which describes things like the way we isolate a single tenant’s information from another’s, how we encrypt and replicate your information, and the way in which your information is protected against and monitored for unauthorized access. All of the documents in our library are living documents which are updated as required.
For more information you can visit: www.office.com/setup365.