Whats new in the Microsoft 365 Roadmap today? 2nd April 2021

Additions : 5
Updates : 9

New FeaturesCurrent Status
Visio: AWS content in Visio desktopIn Development
Outlook: Updates to attachments in received mailIn Development
Outlook: Admin-set organization logos in Outlook for iOS and AndroidIn Development
Microsoft Teams: Teams webinar capabilities general availabilityIn Development
Microsoft Teams: New manage tag experience and other enhancementsIn Development
Updated FeaturesCurrent StatusUpdate Type
Microsoft Teams: Live Transcription with speaker attributionLaunchedStatus
Outlook for Android: Text predictionsLaunchedStatus
Exchange: SMTP MTA Strict Transport Security (MTA-STS) SupportRolling OutStatus
Microsoft Teams: 25K person teamsLaunchedStatus
Outlook: iOS, Android and on the web Extension of suggested replies worldwideLaunchedStatus
Microsoft 365 admin center: Organizational Theme CapabilitiesIn DevelopmentTitle, Description
Office 365: Dictation improvements in Word and Outlook including voice commandsLaunchedStatus
Microsoft Teams: Meeting recordings saved to OneDrive & SharePoint for GCC-High and DoDLaunchedStatus
Microsoft 365: Apps will require Microsoft Edge WebView2 runtimeRolling OutStatus

Regards
The Author – Blogabout.Cloud

Whats new in the Microsoft 365 Roadmap today? 1st April 2021

Additions : 20
Updates : 4

New FeaturesCurrent Status
Azure Active Directory: passwordless authenticationLaunched
Azure Active Directory: Temporary Access PassRolling Out
Azure Active Directory: app gallery experienceLaunched
Azure Active Directory: Microsoft Graph Application Template APILaunched
Azure Active Directory: admin consent workflowLaunched
Azure Active Directory: FS activity and insights reportLaunched
Azure Active Directory: Application Proxy support of header-based authenticationLaunched
Azure Active Directory: Application Proxy traffic optimizationRolling Out
Azure Active Directory: Domain Services replica setLaunched
Azure Active Directory: B2C self-service sign-up user flowsLaunched
Azure Active Directory: B2C Identity Protection & Conditional AccessRolling Out
Azure Active Directory: B2C guest access reviews for Microsoft Teams and Microsoft 365 groupsLaunched
Azure Active Directory: Conditional Access authentication contextRolling Out
Azure Active Directory: secure hybrid access partnershipsLaunched
Azure Active Directory: verifiable credentialsRolling Out
Azure Active Directory: My Apps end user collectionsLaunched
Azure Active Directory: SMS sign-in for frontline workersLaunched
Azure Active Directory: My Staff: delegated management for passwords and phone numbersLaunched
Microsoft Teams: Roaming bandwidth controlIn Development
Microsoft Teams: Separate Window Teams Live Events Producer ExperienceIn Development
Updated FeaturesCurrent StatusUpdate Type
Microsoft Teams: Windows native notifications in TeamsRolling OutStatus
Microsoft 365 Admin Center: Effective Controls for AppsLaunchedStatus
Word for the Web: Text PredictionsLaunchedStatus
SharePoint: Focus mode for modern SharePoint pagesRolling OutStatus

Regards
The Author – Blogabout.Cloud

Invoke-WebRequest: The response content cannot be parsed when adapting a local powershell script for Azure Automation.

I have been recently adapting a PowerShell script that collects the Microsoft 365 Service Health using the Office 365 Service Communication API publishing the information into ServiceNow to log a support ticket to make the helpdesk aware of a potential issue in the service. The script was working is no issues when run manually out of PowerShell ISE but failed when ran by Azure Automation.

The focus of this post is to show two specific steps for adapting a locally executed PowerShell script for an Azure Automation runbook. In addition to standard work in Automation to add credentials/connections and create parameters where needed, the following changes were required to adapt a local script for my runbook.

1) Add -UseBasicParsing to Web Requests

The Management API script is filled with various requests using Invoke-WebRequest. Initially, I received numerous errors stating that the Internet Explorer engine is not available.

Invoke-WebRequest : The response content cannot be parsed because the Internet Explorer engine is not available, or 
Internet Explorer's first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again. 
At line:46 char:9
+ $subs = Invoke-WebRequest -Headers $headerParams -Uri "https://manage ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotImplemented: (:) [Invoke-WebRequest], NotSupportedException
    + FullyQualifiedErrorId : WebCmdletIEDomNotSupportedException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

To overcome this, I needed to add the parameter UseBasicParsing.

Original: $oauth = Invoke-RestMethod -Method Post -Uri $loginURL/$tenantdomain/oauth2/token?api-version=1.0 -Body $body
Adapted: $oauth = Invoke-RestMethod -Method Post -Uri $loginURL/$tenantdomain/oauth2/token?api-version=1.0 -Body $body –UseBasicParsing

2) Alter $ProgressPreference

PowerShell shows progress using $ProgressPreference, which defaults to “continue”. For Automation, I needed to change the option to “silently continue” and suppress progress bars. Locally, the progress can be convenient to see, but it was causing issues with

Automation.Adapted: $ProgressPreference = “silentlyContinue”

Regards
The Author – Blogabout.Cloud

Whats new in the Microsoft 365 Roadmap today? 31st March 2021

Additions : 11
Updates : 26

New FeaturesCurrent Status
Word: Dark ModeIn Development
Word for the Web: Text PredictionsIn Development
Yammer: Nested Replies in YammerIn Development
Microsoft Compliance center: Data loss prevention (DLP) solution overview pageIn Development
Azure Active Directory: Password Protection Enforced for all ChangesIn Development
Microsoft Graph: Graph connectors Results in All tabIn Development
Office 365: Microsoft feedback management controlsIn Development
Microsoft compliance center: New DLP alert management dashboardIn Development
Microsoft Teams: Breakout Room Presenter supportIn Development
Microsoft Teams: New assignment experience in modal window for Breakout RoomsIn Development
Microsoft Teams: Breakout Room pre-meeting room creation and participant assignmentIn Development
Updated FeaturesCurrent StatusUpdate Type
Microsoft Intune: Management of Surface firmware settingsLaunchedStatus
Microsoft Graph: [TEAMWORK] Resource-specific consent API (Preview)LaunchedStatus
Microsoft Graph: [TEAMWORK] Post to Activity Feed API (Preview)LaunchedStatus
Outlook on the Web: More options added to “Insert Link” iconLaunchedStatus
Microsoft Teams: Meeting RecapLaunchedStatus
Microsoft Teams: Microsoft Teams panelsLaunchedStatus
Microsoft Teams: Voice-enabled ChannelsRolling OutStatus
Microsoft Teams: Updated layouts for meetings on AndroidRolling OutStatus
Windows Virtual Desktop: Enable deallocated VMs to start automatically when a user connectsLaunchedStatus
Microsoft Defender for Office 365: Improvements to Alerts and HuntingRolling OutStatus
Outlook for iOS: Extending suggested replies in more languages worldwideLaunchedStatus
Outlook for Android: Extending suggested replies in additional languages world wideLaunchedStatus
SharePoint Syntex: Search inside training files while building document understanding modelsLaunchedStatus
Syntex: Model usage analytics in content centerLaunchedStatus
Outlook: on the web – New location for Outlook modulesRolling OutStatus
Microsoft 365 Compliance Center: Ability to delete a record labelRolling OutStatus
Microsoft 365 Compliance Center | Records management: Increased file plan import limitsLaunchedStatus
Exchange Admin Center: Another User Feature in New EACLaunchedStatus
OneDrive: Quickly change permissions in OneDrive/SharePoint share controls.Rolling OutStatus
Outlook: My Day pane available in Office.comRolling OutStatus
SharePoint Syntex: Document understanding model improvements – extractor rename; model rename & duplication supportLaunchedStatus
SharePoint Syntex: Document understanding model improvements – consolidated explanation typesLaunchedStatus
SharePoint Syntex: Syntex license expiration – disable experiences in UXLaunchedStatus
Microsoft Teams: Forms Polls in Teams Meetings ImprovementsRolling OutStatus
Forms: Split sending and sharing entry pointRolling OutStatus
Office 365: Dictation improvements in Word for Mac including voice commandsCancelledStatus

Regards
The Author – Blogabout.Cloud

Configuring Password Expiry within Microsoft 365 admin center and with PowerShell

In this brief blog post I am going to demonstrate how simple it is to configure or modify password expiry policy within the Microsoft 365 Admin Center or using PowerShell to make the necessary change.

Configure using Admin Center

Launch https://admin.microsoft.com and go to Settings –> Org Settings –> Security & Privacy –> Password expiration policy

Here you can untick Set user passwords to expire which will disable this setting or configure/modify “Days before passwords expire”

Configure using PowerShell

Running the following commands has the same effect as changing the configuration in the Microsoft 365 Admin Center.

# Connect to M365
$cred = Get-Credential
Connect-MsolService -Credential $cred

# Configure Password Policy
Set-MsolPasswordPolicy -ValidityPeriod 60 -NotificationDays 14 -DomainName "contoso.com"

Regards
The Author – Blogabout.Cloud

Quarantined unmanaged mobile devices are when the devices attempt to connect to Exchange Online

In a scenario where an organization takes security as a top priority configuring device quarantine for unmanaged devices will provide a good insight into your user base as well as how secure your corporate email platform is.

Configuring Exchange Online

Launch Exchange Admin Centre https://admin.exchange.microsoft.com/#/homepage

You will now need to switch to Classic Exchange admin center due to the setting required not being visible in the modern admin center.

Select Mobile and click Edit

Tick Quarantine – Let me decide to block or allow later

Click the Add ( + ) button to add Administrators who will receive notifications when a device in quarantined.

Optional – You can include some text which will be provided to the device that has tried to add their mailbox to their personal un-managed device.

Click Save

Once the policy becomes active, you will see devices become quarantined.

This concludes this post

Regards
The Author – Blogabout.Cloud

Ensuring that group owners renew their Office 365 groups every X days

With the increase in usage of Microsoft 365 groups and Microsoft Teams, administrators and users need a way to clean up unused groups and Teams more effectively. A Microsoft 365 groups expiration policy can help remove inactive groups from the system and make things cleaner.

When a group expires, all of its associated services (the mailbox, Planner, SharePoint site, team, etc.) are also deleted.

When a group expires it is “soft-deleted” which means it can still be recovered for up to 30 days.

Modifying the Groups | Expiration

By default, a group has 180 day lifetime and renewal notifications are set to the group owners, 30, 15 and 1 day prior to expiration. Providing 3 chances before the group is removed.

If there are any groups with no owners specified you can configure an email address which will receive the notification renewal alerts.

Now for the most important element, you can configure expiration for all groups, a selection number or not have the setting enabled at all.

Screenshot of Groups expiration settings in Azure Active Directory

Groups that are actively in use are renewed automatically. Any of the following actions will trigger an auto-renew a group:

  • SharePoint – view, edit, download, move, share, or upload files. (Viewing a SharePoint page does not count as an action for automatic renewal.)
  • Outlook – join group, read or write group message from the group, and like a message (Outlook on the web).
  • Microsoft Teams – visiting a Teams channel.
  • Important: The only Yammer activity that will trigger an automatic group renewal is the upload of a document to SharePoint within the community.

Important

When you change the expiration policy, the service recalculates the expiration date for each group. It always starts counting from the date when the group was created, and then applies the new expiration policy.

It’s important to know that expiration is turned off by default. Administrators have to enable it for their organization if they want to use it.

Regards
The Author – Blogabout.Cloud

Whats new in the Microsoft 365 Roadmap today? 30th March 2021

Additions : 6
Updates : 0

New FeaturesCurrent Status
SharePoint: SharePoint News BoostIn Development
Microsoft 365 compliance center: Collection of Teams conversation as transcript in Advanced eDiscoveryIn Development
Microsoft Teams: Admins can install Apps in MeetingsIn Development
Microsoft Teams: Tags are available in GCC HighIn Development
Microsoft Teams: Manage tags in Teams programmatically – Microsoft Teams Tags APIs are now in public previewIn Development
Microsoft Teams: Tags are available in DODIn Development

Regards
The Author – Blogabout.Cloud

Whats new in the Microsoft 365 Roadmap today? 27th March 2021

Additions : 1
Updates : 1

New FeaturesCurrent Status
Office App: Office App for Desktop ImprovementsIn Development
Updated FeaturesCurrent StatusUpdate Type
Microsoft 365 Admin center: Service Health email notifications for specific incidents and advisoriesLaunchedStatus

Regards
The Author – Blogabout.Cloud

Keeping up to date with Microsoft Viva Features – 26th March 2021

With Microsoft Viva becoming more relevant to businesses and organisations I will be publishing a regular post to show whats new on the roadmap.

New FeaturesCurrent Status
Microsoft Viva: Discover experts and answers from TopicsIn Development

Regards
The Author – Blogabout.Cloud

Sitting on a cloud discussing Microsoft Technologies