Office365

[EXO] Exchange Online is depreciating Basic Authentication

If you havent heard already, Microsoft is taking huge steps to improve the overall security in Exchange Online and Office 365 by disabling basic authentication for legacy authentication protocols therein lies the question of “how” to prepare and shift your organization to adopting modern authentication protocols. In the second half of 2021, Microsoft had planned   →

Dictate in Outlook and Office 365*

Try saying “new line”, “new paragraph,” “delete”, “bold that”, and “start list”. Other supported punctuation, commands, and symbols are below. Requirements – microphone access and reliable internet connection – Windwos 10+ – Office 2016+ with Office 365 subscription Supported: Word for Microsoft 365 Outlook for Microsoft 365 PowerPoint for Microsoft 365 Word for Microsoft 365 for Mac PowerPoint for   →

[EXO] Inbox Rule Issues Post Migration

In some instances, users with client side rules may  break as they do not get touched in the migration. For any client rules that reference a specific sender/folder/etc they will normally use X500/LegacyDN to identify conditions and will stop working. There is no set limit for the amount of Inbox rules a user can have.   →

[EXO] Identifying Validation Errors

$errors = (Get-MsolContact –ObjectID <Object_ID>).Errors $errors | foreach-object {“nService: ” + $_.ErrorDetail.Name.split(“/”)[0]; “Error Message: “+ $_.ErrorDetail.ObjectErrors.ErrorRecord.ErrorDescription} $errors = (Get-MsolGroup –ObjectID <Object_ID>).Errors $errors | foreach-object {“nService: ” + $_.ErrorDetail.Name.split(“/”)[0]; “Error Message: “+ $_.ErrorDetail.ObjectErrors.ErrorRecord.ErrorDescription} $errors = (Get-MsolUser -UserPrincipalName “<User_ID>”).Errors $errors | foreach-object {“`nService: ” + $_.ErrorDetail.Name.split(“/”)[0]; “Error Message: ” + $_.ErrorDetail.ObjectErrors.ErrorRecord.ErrorDescription} Get-MsolUser -HasErrorsOnly -All | ft DisplayName,UserPrincipalName,@{Name=”Error”;Expression={($_.errors[0].ErrorDetail.objecterrors.errorrecord.ErrorDescription)}}   →

[EXO] The client and server cannot communicate, because they do not possess a common algorithm

Windows Server 2008 can’t do beyond TLS 1.0. Newer versions can, but don’t have TLS 1.1 or 1.2 turned on by default. Best pratice to disable 1.0, 1.1 – mostly depreciated and not supported Check supported protocols: https://www.ssllabs.com/ssltest/index.html Turn off TLS 1.0.1.1 and SSL

Enabling TLS 1.2 Use

 

[EXO][EX2010] Removing dual mailboxes

Ensure you have a user mailbox backup prior to starting the following process as there is potential risk of data loss.  Options are to have a third party solution to perform a mailbox backup or export to PST (see new-mailboxexport cmdlet). Capture relevant information from on-premise exchange and exchange online. Grab the mailbox information (primary   →

[EX2010][EXO] Forwarding Address Export and Import

 

[O365][PS] Exchange Online Powershell Module and connecting to Exchange Online

Example 1:

Example 2:

 Troubleshooting Errors: New-ExoPSSession : user_realm_discovery_failed: User realm discovery failed

Check proxy settings in IE New-ExoPSSession: The SSL certificate could not be checked for revocation.

Set winhttpbyusingsetproxycommand: Show: netsh winhttp show proxy Set Proxy: netsh winhttp set proxy <proxy url or ip>:<port> Reset Proxy: netsh winhttp reset proxy   →