Genesis Group

Tenant Discontent

Not everyone reads Microsoft marketing posts (or the copies of the content reposted in the technical press), nor is everyone aware of Office 365 notifications (which is why it’s a good idea to synchronize notifications into Planner). Tenant administrators are often so busy that they only respond when directly contacted. Mutterings of discontent duly emerged in some parts of the Office 365 community last week when tenant administrators received a preview of the Cortana daily briefing email (Figure 1). The message gives two weeks’ notice of the arrival of daily briefings into user mailboxes. I got the update for my tenant on Thursday and therefore anticipate that users will start receiving daily briefings at the end of June.

Image 1 Expand 

The Purpose of the Cortana Daily Briefing

According to Microsoft, Cortana’s daily briefing will:

• Help users to be (better) prepared for meetings by finding related documents and messages and including those items in the briefing email.
• Follow up on commitments by highlighting requests and commitments from email (MyAnalytics already does this).
• Protect time by blocking out slots in user calendars for dedicated tasks (again, something that MyAnalytics does).

Users won’t receive daily briefings unless Cortana can come up with at least one actionable item. I guess this means that people won’t ever be reassured by Cortana that they can take the day off.

The preview message reassures administrators that the daily briefing respects user privacy and is GDPR compliant. This is correct because the information is delivered to the user and not shared with anyone else and is derived from information available in their Exchange Online mailbox, which again isn’t shared with anyone else, again like MyAnalytics.

Reading the above, it should come as no surprise that the daily briefing comes courtesy of the same group that’s responsible for MyAnalytics, which has been concentrating on using data to drive user insights for the last few years. Many of the same insights will now appear in daily briefings.

Daily Briefing Should Be Opt-In

Some will delight in the new functionality. Others will think it an unwarranted intrusion into user privacy being fostered on Office 365 users by Microsoft.

Once again, Microsoft has chosen to introduce a feature without a tenant-wide turn-off switch. Like MyAnalytics, users can opt-out (by unsubscribing) if they don’t want to receive these messages. Or administrators can take action to stop users receiving the messages in the first place by running some PowerShell.

Disabling the daily briefing, at least temporarily, seems like a sensible thing to do because we know from experience with MyAnalytics that many organizations are unprepared for the advent of automated advice. Users are untrained, don’t know what to do with the recommendations, or simply don’t like being told what to do with their working lives. An idea that seems great in the confines of a Redmond conference room can be difficult to transfer to real life.

MyAnalytics used to be only available in Office 365 E5 or as an add-on for Office 365. When that was the case, organizations had the chance to decide whether MyAnalytics should be used and could prepare their users. Microsoft then decided to make MyAnalytics available to all Office 365 enterprise and business customers, which provoked many questions how to stop MyAnalytics messages reaching users.

Microsoft received this feedback – several times, including by me (several times). But they decided to persist and impose their vision of how people should work intelligently on an Office 365 user base that is now so large and diverse that it’s almost impossible to get agreement on how anything should be done, which is why opt-in is better than opt-out.

Disabling Cortana’s Daily Briefing with PowerShell

Once you receive the heads-up that the daily briefing is on its way, you should consider who might like to receive it. And for those that don’t, you can disable the daily briefing by running the PowerShell Set-UserBriefingConfig cmdlet, part of the new Exchange Online management module. One trivia point about Set-UserBriefingConfig: it is the first Exchange REST-based cmdlet to update mailbox settings – all the other REST-based cmdlets fetch information.

Set-UserBriefingConfig works by enabling or disabling the feature for a mailbox. To disable the daily briefing for a specific user, run a command like:

Set-UserBriefingConfig -Identity Kim.Akers@Office365itpros.com -Enabled $False

It’s more likely that you’ll need to disable the daily briefing for groups of users. You can form collections of mailboxes to process with cmdlets like Get-ExoMailbox. For example, this code finds all user mailboxes and disables them for the daily briefing, the rough equivalent of disabling the feature for an entire tenant:

$Accounts = Get-ExoMailbox -ResultSize Unlimited -RecipientTypeDetails UserMailbox
ForEach ($Account in $Accounts) { Set-UserBriefingConfig -Identity $Account.UserPrincipalName -Enabled $False }

Unfortunately, the Set-UserBriefingConfig cmdlet doesn’t accept piped input from Get-ExoMailbox, which is why a loop is needed to process the collected mailboxes. Remember that the daily briefing will need to be disabled after adding new mailboxes. This can’t be done in a mailbox plan. 

Subscribe to Petri NewslettersOffice 365 Insider

Sometimes you’ll need to refer to properties that are held in Azure AD rather than Exchange Online, like country or department. For example, here’s how to disable the daily briefing for everyone in a chosen country.

$Country = Read-Host "What country do you want to disable the daily briefing for"
$Accounts = Get-AzureADuser -All:$True -Filter "Country eq '$Country' and UserType eq 'Member'"
If (!$Accounts)
  { Write-Host "No accounts found in" $Country; break}
Write-Host "Finding mailboxes in the" $Accounts.Count "accounts found in" $Country
ForEach ($Account in $Accounts) {
  If (Get-ExoMailbox -Identity $Account.ObjectId -RecipientTypeDetails UserMailbox -ErrorAction SilentlyContinue) {
    Write-Host "Processing" $Account.DisplayName 
    Set-UserBriefingConfig -Identity $Account.UserPrincipalName -Enabled $False }
}

The Get-UserBriefingConfig cmdlet is available to check the daily briefing status of mailboxes:

Get-UserBriefingConfig -Identity Ben.James@Office365itpros.com

UserId                        IsEnabled
------                        ---------
Ben.James@Office365itpros.com     False

Time to Break the Bad Habit

Microsoft has a bad habit of deciding how Office 365 tenants should consume data, like creating Microsoft 365 groups for managers and their direct reports, thinking that allowing users to self-purchase PowerAutomate licenses was a good idea, or deciding that small organizations would like an org-wide team.

I’m not against the wider application of artificial intelligence and machine learning to smarten the way we work and it’s great to have practical examples of these technologies. However, Microsoft should respect the right of Office 365 tenants to decide when technology is used instead of being forced on people by assuming everyone will be happy to receive Cortana’s daily briefing.

The post Cortana Daily Briefing Not Wanted by Some Office 365 Tenants appeared first on Petri.