Office 365 Message Encryption Encrypt messages to any

Office 365 Message Encryption – Encrypt messages to any SMTP address Personal account statement from a financial institution Information Rights Management – Encrypt content and restrict usage; usually within own organization or trusted partners Internal company confidential memo S/MIME – Sign and encrypt messages to users using certificates Peer to peer signed communication within a government agency

Admin: • • Simple to provision and configure Policy driven via Transport Rules Customizable branding of encrypted emails and mail reading portal Allows for Enterprise content inspection and compliance Sender: • Ability to send encrypted messages to any SMTP address regardless of recipient’s client or service provider Recipient: • • • View encrypted messages on Office 365 Message Encryption portal after sign-in Office 365 Message Encryption portal has rich OWA controls for viewing and composing messages Replies from the portal are also encrypted

How do recipients sign-in to view messages? – 2 ways • Microsoft account – used for sign-in to Microsoft services like One. Drive, XBOX Live, etc… • Microsoft account for hotmail. com, outlook. com, live. com already exists • User can create Microsoft account for any SMTP address, like gmail. com, mycustomdomain. com – address verification done as part of account creation process • If recipient does not have a Microsoft account, recipients are navigated through the process of creating one • For a given email address, a single Microsoft account is used to access all Microsoft services and view future encrypted emails • Organizational Account – used for sign-in to workloads like Exchange Online, Share. Point Online, etc… • As Office 365 embraces additional identity providers, so will Office 365 Message Encryption.

• New ETR actions configurable via UI or Power. Shell New-Transport. Rule –Name Encrypt. Rule <Condition for which to apply encryption> -Apply. OME $true New-Transport. Rule –Name Decrypt. Rule <Condition for which to remove encryption> -Remove. OME $true

• Customize opening text in encrypted email and disclaimer statement Set-OMEConfiguration -Identity default -Email. Text "Encrypted message from Contoso. Pharma secure messaging system" Set-OMEConfiguration -Identity default -Disclaimer. Text “This email message and its attachments are for the sole use of the …"

Set-OMEConfiguration -Identity default -Portal. Text "Contoso. Pharma secure e-mail portal" Set-OMEConfiguration -Identity default -Image (Get-Content "C: UsersadminDesktopcontoso. png” -Encoding byte)

Exchange Online Policy detection and Enforcement O 365 User Delive d Sen r Internet User Mail Reading Portal t Pos Tenant configuration Microsoft account/Organization Account

• Office 365 Message Encryption uses IRM as a platform to encrypt message • Sending organization needs to have purchased and configured Azure Rights Management Services (RMS) • Keys imported from Azure RMS are 2048 bit and use SHA-256 encryption • Encrypted messages are wrapped in an HTML file and sent as an attachment to intended recipients • HTML file contains the encrypted message along with other metadata • Messages can be viewed on any device that can open and post from an HTML file • When user opens and clicks on link in the attachment, encrypted content is posted and held temporarily while user authenticates • User authenticates using a Microsoft account or Organizational Account • If user has neither, user is told and asked to create a Microsoft account before viewing • Any email address (@yahoo. com, @gmail. com, etc…) can be used to create a Microsoft account • Once the authentication completes, message is decrypted and shown in modern UI with all rich OWA controls • Messages replied from the portal are also encrypted

Office 365 Message Encryption is included with Azure RMS Plan Requires Price Office 365 E 3, E 4 Windows Azure Rights Management is included Included Office 365 E 1, K 1 Windows Azure Rights Management $2 PUPM Office 365 Exchange Online Plan 2, Plan 1, Kiosk Windows Azure Rights Management $2 PUPM Office 365 Share. Point Plan 2, Plan 1 Windows Azure Rights Management $2 PUPM Office 365 Midsize Business Windows Azure Rights Management $2 PUPM Exchange on-premises Windows Azure Rights Management $2 PUPM * On-premise customers need to route mails through Exchange Online ** Windows Azure Rights Management is not available for Office 365 Small Business plans

• Customers using EHE will be upgraded to Office 365 Message Encryption at • • no additional cost Awareness and transition emails will be sent prior to transition – Transitions started for Q 1 CY 14 No action required on tenant admins – existing EHE policies will be automatically migrated to Office 365 Message Encryption policies EHE mail recipients will continue to have access to view their old encrypted emails EHE account store and emails already encrypted with EHE will not be migrated to Office 365 Message Encryption

Feature Exchange Hosted Encryption Office 365 Message Encryption Send Encrypted Mail to anyone Available Custom Branding Not Available Message attachment size limit 10 MB 25 MB Integration with Exchange transport rules Available, but complex headers involved Available and simplified User experience Custom EHE portal Enhanced Office 365 UI Integration with Data Loss Prevention Available Purchase Option Sold Standalone Included with Azure RMS

• Information Protection technology • Protection is persisted with the data, content can travel anywhere (desktops, file shares, USB keys, cloud drives, network and devices) • Combines encryption and usage restrictions • Prevent accidental disclosure of sensitive data by applying usage polices (cannot forward, cannot print, read-only) • Simple to use • Authors just select a policy option, consumers just open documents • Administrators can configure policies to protect content automatically • Securely share data with individuals within organization and trusted partners

Admin: • Simple to provision and configure using Windows Azure Rights Management – No on- premises RMS server required • Policy driven via Transport Rules • Allows for Enterprise content inspection and compliance Sender: • Ability to send IRM protected messages to recipients in the organization using supported clients - OWA and Microsoft Office 2010 and 2013 Recipient: • Ability to view IRM protected content just like regular emails using supported clients (OWA, Microsoft Office 2010 and 2013, EAS)

• Automatically protect email with IRM using Exchange Transport Rules

• Protect email with IRM right from the Outlook Web App.

Government preferred way to secure email communication • • Based on a published and broadly supported standard Must know recipients public cert to send them encrypted mail Must have private key associated with sending email address to sign email Without having recipients private key, no one can open and view the message Exchange on-prem continues to support S/MIME OWA 2013 support added in SP 1

Admin: • Admin provisions certificates to users and synchronizes them with Exchange Online • Simple Exchange Online configuration for S/MIME OWA behavior Sender: • Ability to send signed and encrypted email to intra organization recipients who are properly configured Recipient • Ability to view signed and encrypted emails using OWA and supported clients and reply

• Admin Exchange Online configuration options

Office 365 Message Encryption – Encrypt messages to any SMTP address Personal account statement from a financial institution Information Rights Management – Encrypt content and restrict usage; usually within own organization or trusted partners Internal company confidential memo S/MIME – Sign and encrypt messages to users using certificates Peer to peer signed communication within a government agency