아래의 내용은 ChatGPT가 정리하여 작성한 내용입니다.
Message ID MC455516는 Microsoft Purview Message Encryption과 관련된 변경사항에 대해 다룹니다. 주요 내용은 다음과 같습니다:
- 업데이트 개요:
- 2024년 1월 2일에 Microsoft Purview Message Encryption과 관련된 변경사항의 타이밍이 업데이트되었습니다.
- 은퇴 후에도 Microsoft Purview Message Encryption으로 보호된 공유 메일박스로 보낸 암호화된 메일에는 Outlook 웹에서 메일을 열 수 있는 링크가 포함됩니다. 이것은 Office 365 Message Encryption을 사용하여 보호된 메시지를 여는 유사한 방식을 제공합니다.
- 출시 일정:
- 표준 출시: 2024년 1월 초에 시작하여 1월 말에 완료될 예정입니다.
- 조직에 미치는 영향:
- Microsoft Purview Message Encryption은 내부 및 외부 조직의 모든 사람에게 암호화된 메일을 제공하는 더 안전하고 유연한 솔루션입니다. 수신자에게 향상된 사용자 경험을 제공합니다.
- OME의 경우, 모든 수신자는 암호화된 메일을 열기 위해 HTML 첨부 파일을 받았지만, 이제는 Microsoft 365 사용자가 Outlook 클라이언트에서 메시지를 인라인으로 볼 수 있습니다. Microsoft 365 사용자가 아닌 사람들은 대신 메일을 열기 위한 링크 기반의 경험을 받게 됩니다.
- 지원되는 첨부 파일은 다운로드 시에도 암호화되어 휴식 상태에서의 민감한 데이터를 보호합니다.
- 준비사항:
- 단종되기 전에 동작을 비교하고 싶다면, 다음 문서에 제시된 단계를 따라 메일 흐름 규칙을 수정하고 테스트할 수 있습니다: Define mail flow rules to use Microsoft Purview Message Encryption (https://learn.microsoft.com/microsoft-365/compliance/set-up-new-message-encryption-capabilities?redirectSourcePath=%252fen-us%252farticle%252fSet-up-new-Office-365-Message-Encryption-capabilities-built-on-top-of-Azure-Information-Protection-7ff0c040-b25c-4378-9904-b1b50210d00e&view=o365-worldwide#next-steps-define-mail-flow-rules-to-use-microsoft-purview-message-encryption)
요약하면, 이 업데이트는 Microsoft Purview Message Encryption으로의 전환과 관련된 여러 변경사항을 포함합니다. 이 변경사항은 암호화된 메일의 제공 및 관리 방법을 향상시키며, 이로 인해 조직 내에서 더 나은 보안과 사용자 경험을 제공합니다.
원문 메시지
Message ID: MC455516
Published date: 2022-11-04
Last updated date: 2024-01-02
Category: 변경 계획
Tags: 주요 업데이트, 관리자 영향, 사용자 영향, 은퇴
Updated January 2, 2024: We have updated the timing of this change below.After retirement, any encrypted mail sent to shared mailbox protected with Microsoft Purview Message Encryption will have a link that can open the mail in Outlook on the web. This provides an equivalent flow to open messages protected using Office 365 Message Encryption.
As a reminder, the following PowerShell cmdlet parameter will be retired in New/Set-Transport rule cmdlet: -ApplyOME -RemoveOME
Note: If you use the Exchange Admin Center to create/modify a mail flow rule, the action will fail with a message to indicate the above functions have been retired.Microsoft Purview Message Encryption will replace and retire the legacy Office 365 Message Encryption (OME) in the Exchange admin center. If you don’t do anything, Microsoft will process all mail flow rules that currently applies OME protection to Microsoft Purview Message Encryption protection. With this change, recipients will receive a much more customizable notification mail. Retirement of OMEv1 is coming in 2 phases
on June 30th OMEv1 mail flow rules become read-only or delete-only. No new rules or rule modifications will be allowed. These rules will be encrypt/decrypt with OMEv1
mid-January 2024 (previously) the OME v1 mail flow rules will be fully retired. All the OMEv1 rules will be automatcially process as OMEv2
For customers who need an exception to do OMEv1 mail flow rule updates between June 30th and Dec 31st, open a support ticket to request the exception.Finally, we recommend all customers that use OMEv1 to receive email into a shared mailbox we highly recommend requesting the exception. We are targeting to release additional changes in Q3CY23 that will improve the shared mailbox experience.
[How this will affect your organization:]
Microsoft Purview Message Encryption is a more secure and flexible solution to provide encrypted mail to anyone inside or outside your organization, with an enhanced user experience for recipients. For example, with OME, all recipients receive an HTML attachment to open an encrypted mail. This has been greatly improved with Outlook clients for Microsoft 365 users who can now view the message inline. Non-Microsoft 365 users will instead receive a linked-based experience to open the mail. Additionally, supported attachments are also encrypted on download to protect sensitive data at rest. Office 365 Message EncryptionMicrosoft Purview Message EncryptionThe behavioral differences and different types of recipients are described in the following table.
Currently OME mail flows
Deprecated OME mail flows
Mail body branding
“Office 365 Message Encryption"
“Microsoft Purview Message Encryption"
Internal M365 recipients experience
Any client will contain an html attachment, open the attachment to open mail in OME portal.
Supported Outlook client with inline experience with a message.rpmsg.
Any unsupported client will show notification mail with URL link to open mail in Outlook on the Web. (This is also true for users on Exchange on-premises mailbox."
External M365 recipients experience
Any client will contain an html attachment, open the attachment to open mail in OME portal.
Any client will show notification mail with URL link to open mail in Microsoft Purview encrypted message portal; there is no attachment in mail.
Mail flow rules can be modified to provide same behavior as internal recipients above.**
(External) Non-M365 recipients experience
Any client will contain an html attachment, open the attachment to open mail in OME portal.
After mail is opened in the portal, mail and attachment can be viewed.
All attachments are downloaded without encryption
Any client will show notification mail with URL link to open mail in Microsoft Purview encrypted message portal; there is no attachment in mail.
After mail is opened in the portal, mail and attachment can be viewed.
Office documents are downloaded with encryption if no changes are made by admins.*
*The encrypted attachments provide extra security by protecting the stored file at rest. Applications that can open Office documents may not be compatible with RMS protected Office documents. Admins can provide the same behavior as OME by enabling a global configuration to download Encrypt-only attachments without encryption: Set-IrmConfiguration – DecryptAttachmentForEncryptOnly $true
**By modifying existing the mail flow rules to apply Purview Message Encryption protection, external M365 recipients will receive encrypted mail containing a message.rpmsg attachment and supported Outlook clients can provide show the mail content directly in the application.
[What you need to do to prepare:]
If you want to compare the behavior before the deprecation, you can modify and test the changes with your mail flow rules by following the steps outlined in this documentation: Define mail flow rules to use Microsoft Purview Message Encryption (https://learn.microsoft.com/microsoft-365/compliance/set-up-new-message-encryption-capabilities?redirectSourcePath=%252fen-us%252farticle%252fSet-up-new-Office-365-Message-Encryption-capabilities-built-on-top-of-Azure-Information-Protection-7ff0c040-b25c-4378-9904-b1b50210d00e&view=o365-worldwide#next-steps-define-mail-flow-rules-to-use-microsoft-purview-message-encryption)Learn more: How Microsoft Purview Message Encryption works (https://learn.microsoft.com/microsoft-365/compliance/ome?view=o365-worldwide#how-message-encryption-works)