In order to better protect our customers from exact domain spoofing attacks and improve deliverability of email, we are making changes to how we handle DMARC p=reject and p=quarantine.

For the enterprise customers, we are also making updates to how DMARC policy-based reject can be handled. This change will help Security Administrators be able to choose how DMARC policy-based reject and quarantine can be applied within their organization. 

For the consumer service, this means that if an email fails DMARC validation, it will be dropped and will not be delivered to the recipient’s inbox. This change will help to ensure that only emails from verified senders are delivered to our customers’ inboxes.

This message is associated with Microsoft 365 Roadmap ID 117533

When this will happen:

Standard: Rollout will begin in late April 2023 and is expected to be complete by mid-May 2023.

Gov Cloud: Rollout will begin in mid-April 2023 and is expected to be complete by mid-June 2023.

How this will affect your organization:

For enterprise customers, within the actions section of the Anti-Phishing policy, the new setting to honor DMARC policy will be disabled by default. In this case, currently if DMARC p=reject, the action specified when spoof intelligence detects a message is applied. (Note: it is set to go to junk by default). 

Moving forward, using the updated actions for spoof intelligence settings within the Anti-Phishing policy, the recipient tenant admin will be able to choose how they want to honor DMARC policy settings. 

What you need to do to prepare:

If the tenant admin chooses to enable this new setting to honor DMARC policy, by default, the action applied will be “quarantine” in case of DMARC p=reject or p=quarantine. The tenant admin can change it as desired to either “reject” or “junk” the message instead (respectively).

If you wish to honor DMARC, before turning on the feature, you may choose to review spoof intelligence insight to identify legitimate senders who are sending DMARC reject or quarantine emails. Based on your organization’s email sending business, you may override the sender domain pairs to the Tenant allow block lists – Spoofed Senders. You may want to notify your users about this change and update your training and documentation as appropriate.

Message ID: MC543870

The post Microsoft Defender for Office 365: DMARC Handling appeared first on M365 Admin.

We are thrilled to share the exciting news that the rebranding of Yammer and all its surfaces is nearly complete! The Yammer website, the SharePoint and embed integrations, as well as the Power Automate integration rebranding will take place during the last week of June of 2023.

This message is associated with Microsoft 365 Roadmap ID 117366

When this will happen:

We will begin rolling out in early May 2023 and complete by late June 2023.

How this will affect your organization:

There will be no impact to the existing profile, posts, bookmarks, etc. All rebranding updates don’t require additional actions; changes will be automatic. Outside of branding changes, there are no changes to the features, capabilities, and investments for Microsoft 365 customers. You will continue to experience and benefit from all the powerful features of Viva Engage just as you did with Yammer.

To ensure all users are fully informed and engaged in this stage of the rebranding process, we have developed an exciting in-product announcement plan that will provide key information at specific moments.

Our announcement plan is tailored to specific audiences, and it’s structured into two phases: prior the website rebranding and on the website rebranding date.

As shared in previous posts, to help make the transition as smooth as possible, we have also created a rebranding toolkit that includes a range of templates, logos, and other resources to help communicate the change. It can be found – here

Before the rebranding date

1. Reminder banner only visible to network admins

View image in new tab

1. We will begin rolling out in early May 2023 a dismissible banner on our website that will only be visible to network admins. The banner has been designed to serve as a helpful reminder to admins of the upcoming change and provide them with a convenient link to the rebranding toolkit, which contains valuable resources to assist them in effectively communicating the change to their teams.
2. Heads-up banner visible to all users

View image in new tab

1. This banner will be displayed on the website and will be visible to all users. Its purpose is to provide a heads-up to users about the upcoming change and prepare them for what’s to come. We will begin rolling out this banner mid-June 2023, two weeks prior to the rebranding date.

On the rebranding date

1. Announcement dialog on the website

View image in new tab

1. We will roll out in late June, the day of the rebranding, an announcement banner. Users who access the website will be greeted with a welcoming dialog that will inform them of the brand name change. Once users dismiss the dialog, they will be able to access the rebranded experience.
2. Announcement banner on email digests

View image in new tab

1. In addition to the website dialog, we want to ensure that users who consume content through email are also made aware of the rebranding. To achieve this, we have included a banner in the digests that will be visible for a period of two weeks. We will begin rolling out this banner late June 2023.

What you need to do to prepare:

There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.

Message ID: MC541154

The post In-product announcements for the Yammer website rebrand to Viva Engage appeared first on M365 Admin.

We are updating the chat details experience for Teams Mobile Group Chats, One on One Chats, and Self Chats. 

This message is associated with Microsoft 365 Roadmap ID: 114938

When this will happen:

Targeted Release (Preview): We will begin rolling out in mid-April and expect to complete rollout by mid-May.

Standard Release: We will begin rolling out in mid-April and expect to complete rollout by mid-May.

GCC, GCC-H, DoD: We will begin rolling out in late May and expect to complete rollout by early June.

How this will affect your organization:

The following items will be new:

• Updated UI and layout.
• Users are now able to access their own people card from the chat details and see Files and Apps from that conversation rather than seeing Files and Apps from the chat canvas, which will be deprecated.

View image in new tab  View image in new tab

What you need to do to prepare:

There is no action required at this time. You may want to notify your users of this change. 

View image in new tab

Message ID: MC537952

The post Microsoft Teams for Mobile: Chat Details Update appeared first on M365 Admin.