Microsoft Teams arrives to Office ProPlus, so what do I need to know

By Author on June 12, 2019June 12, 2019Leave a Comment

As a big advocate for Office ProPlus I am delighted to now see that Microsoft Teams now apart of the ProPlus deliver mechanism. However, just like any Microsoft product, it does have its caveats.

Microsoft Teams will only be included with NEW installations of Office 365 ProPlus dependent on the channel you are using. The below shows the schedule of the introduction but this is subject to change.

Update channel	Version	Date
Monthly Channel	Version 1902	March 4, 2019
Semi-Annual Channel (Targeted)	Version 1902	March 12, 2019
Semi-Annual Channel	Version 1902	July 9, 2019

Important Note:
Teams are also included with the following new installations:
Office 365 Business, starting with Version 1901, which was released on January 31, 2019. Office 365 Business is the version of Office that is included with certain business plans, such as the Microsoft 365 Business plan and the Office 365 Business Premium plan.

Office for Mac, starting with Version 16.21, which was released on January 16, 2019. Office for Mac comes with any plan that includes Office 365 Business or Office 365 ProPlus. For more information, see Microsoft Teams installations on a Mac.

Now Microsoft Teams is apart of the Office Deployment tool it is now subject to all the controls we are common use to so we exclude Teams if we really to 🙂 but why would we do that.

What about existing deployments of Office 365 ProPlus?

At the time of this post, it is not possible to get Microsoft Teams if you have an existing deployment of Office 365 ProPlus. Microsoft has announced that in Version 1906 Microsoft Teams will be shipped to existing deployment running this version. The table below gives an indication of when we can expect the rollout of Teams but if you are using Monthly Channel (Targeted) you should be seeing Microsoft appearing approximately on 25th June 2019.

Update channel	Version	Date
Monthly Channel	Version 1906	July 9, 2019
Semi-Annual Channel (Targeted)	To be determined	September 10, 2019
Semi-Annual Channel	To be determined	January 2020

If you don’t want Teams to be added to existing installations of Office 365 ProPlus when you update to a new version, you can use Group Policy or the Office Deployment Tool to exclude the installation.

Always keep up to date.
Make sure you’re using the most current version of the Office Deployment tool available on the Microsoft Download Center.

Be sure you’re using at least version 4867.1000 of the Administrative Template files (ADMX/ADML), which were released on June 7, 2019.

Temporarily, the name and help text for this policy setting is available only in English. The name and help text will be available in the usual set of languages by June 14, 2019.

Updating Microsoft Teams !! It doesnt follow the normal ProPlus cycles.

Once Microsoft Teams is installed, it automatically updates approximately every two weeks with new features and quality updates. This doesn‘t follow the normal update cycle for Office 365 ProPlus as other applications receive updates depending on which channel they’re on.

Regards
The Author – Blogabout.Cloud

New functionality now in preview for Conditional Access

By Author on May 17, 2019May 17, 2019Leave a Comment

So I was happily minding my own business looking at the configuration of my Conditional Access and notice 3 new options have appeared;

Baseline policy: End user protection (Preview)
Baseline policy: Block legacy authentication (Preview)
Baseline policy: Require MFA for Service Management (Preview)

Baseline policy: End user protection (Preview)

This policy protects users by requiring multi-factor authentication (MFA) during risky sign-in attempts to all applications. Users with leaked credentials are blocked from signing in until a password reset.

Once the policy is enabled, users are required to register for MFA within 14 days of their first login attempt. The default method of MFA registration is the Microsoft Authenticator App.

This policy is either On or Off and you can also exclude users from receiving this policy

Baseline policy: Block legacy authentication (Preview)

This policy blocks all sign-ins using legacy authentication protocols that don’t support multi-factor authentication (such as IMAP, POP, SMTP). The policy does not block Exchange ActiveSync.

Office 2013 (without registry keys)
Office 2010
Thunderbird client
Legacy Skype for Business
Native Android mail client

This policy is either On or Off and you can also exclude users from receiving this policy. This policy is great as I have configured a custom built policy for just this but my policy also includes Exchange Active Sync.

Baseline policy: Require MFA for Service Management (Preview)

This policy requires users logging into services that rely on the Azure Resource Manager API to perform multi-factor authentication (MFA).

Services requiring MFA include:

Azure Portal
Azure Command Line Interface (CLI)
Azure PowerShell Module

This policy is either On or Off and you can also exclude users from receiving this policy

Its great to see some more brilliant developments in Conditional Access and really excited to see these go live with customers.

Regards
The Author – Blogabout.Cloud

HCW8078 – Migration Endpoint could not be created

By Author on May 7, 2019May 8, 2019Leave a Comment

Quicktips: Notes from the field

While running the Exchange Hybrod Configuration Wizard I ran in the following issue;

HCW8078 – Migration Endpoint could not be created
Microsoft.Exchange.Migration.MigrationServerConnectionFailedException
The connection to the server ‘http://mail.domain.com’ could not be complete

This issue is a known issue to Microsoft and the resolution is the good old “Have you tried turning it off and on?”

The It Crowd Chris Odowd GIF - Find & Share on GIPHY

The resolution was to Disable MRSProxyEnabled, this can be easily completed for all servers using;

Get-WebServiceVirtualDirectory | Set-WebServiceVirtualDirectory -MRSProxyEnabled $False

Get-WebServiceVirtualDirectory | Set-WebServiceVirtualDirectory -MRSProxyEnabled $True

This script will need to repeat this process for all your servers where MRSProxy is being used.
Invoke-Command -ComputerName Server1 -ScriptBlock {iisreset /restart}

Once you have completed the below steps you will be able to successful rerun the Hybrid Configuration Wizard without any errors

Regards
The Author – Blogabout.Cloud

The pain in the a** that is special characters. Understanding what is and isnt supported when migrating to the Microsoft Cloud.

By Author on April 12, 2019April 12, 2019Leave a Comment

So in recent months, I have been working a number of large organisation that have issues with special characters that are affecting their migration to the Microsoft Cloud. Yes, I IDFix does an excellent job of correcting a lot of the issues. However, in recent time I have been rolled into customer sites to troubleshoot and report on special characters contained in Distribution Lists and Shared Mailboxes which cannot be migrated to Exchange Online.

What special characters are supported in Office 365?

So first of all, what is and is not supported. The below table gives an excellent break down what the character can be supported in UserNames, Password and Email Addresses.

Allowed In
Character Name	Character	User Name	Password	Email Address
Accent	`	No	Yes	No
Ampersand	&	No	Yes	No
Angle Brackets	< >	No	Yes	No
Apostrophe	’	No	Yes	Yes***
Asterisk	*	No	Yes	No
At Symbol	@	No	Yes	No
Backslash	\	No	Yes	No
Braces	[ ]	No	Yes	No
Brackets	{ }	No	Yes	No
Circumflex	^	No	Yes	No
Colon	:	No	Yes	No
Comma	,	No	Yes	No
Dollar Sign	$	No	Yes	No
Equal Sign	=	No	Yes	No
Exclamation Point	!	No	Yes	No
Hyphen	–	Yes*	Yes	Yes*
Number Sign	#	No	Yes	No
Parentheses	( )	No	Yes	No
Percent Symbol	%	No	Yes	No
Period	.	Yes*	Yes	Yes*
Pipe	\|	No	Yes	No
Plus Sign	+	No	Yes	No
Question Mark	?	No	Yes	No
Quotation Mark	“	No	Yes	No
Semicolon	:	No	Yes	No
Forward Slash	/	No	Yes	No
Tilde	~	No	Yes	No
Underscore	_	Yes**	Yes	Yes**
Uppercase Letters (A-Z)	A-Z	Yes	Yes	Yes
Lowercase Letters (a-z)	a-z	Yes	Yes	Yes
Numerals (0-9)	0-9	Yes	Yes	Yes

In order to test for the special characters above I have created the following script


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
cls

 $array = @('~', '!', '#', '$', '%', '^', '&amp;', '(', ')', '-', '.+', '=', '}', '{', '\', '/', '|', ';', ',', ':', '&lt;', '>', '"')

 $samaccountarray = @('[', '\', '"', '|' , ',' , '/', ':', '&lt;', '>', '+', '=', ';', ']')

 foreach ($char in $array) {

 Write-Host "Please Wait... Detecting",$char," in samaccountname" -ForegroundColor Yellow

 $objects = Get-distributiongroup

 foreach ($object in $Objects)

 {

 try {

  if ($object.SamAccountName -like "*$char*") 

 {

 Write-Host "Special Character",$char,"detected in SamAccountName",$object.samaccountname -ForegroundColor Red

 

 }

 else

 {

 #Write-Host "Special Character",$char," not detected in " $object.UserPrincipalName

 }

 }

 catch

 {

 Write-Host "Great News!! we was unable to detect",$char,"in samaccountnames for all Distribution List" -ForegroundColor Green

 }

 }

 }

Get-SpecialCharacters (24 downloads)

If you are interested in understanding what IDFix does and what special characters are not supported, please see this link

https://docs.microsoft.com/en-gb/office365/enterprise/prepare-for-directory-synchronization?redirectSourcePath=%252fen-us%252farticle%252fPrepare-to-provision-users-through-directory-synchronization-to-Office-365-01920974-9e6f-4331-a370-13aea4e82b3e

Regards

The Author – Blogabout.Cloud

Configuring Outbound Delivery Routing from Office 365 to Mimecast

By Author on April 4, 2019April 5, 2019Leave a Comment

When working with customer environments it is very possible a 3rd party appliance maybe involved and for the purpose of this post I will be directly looking at Mimecast to see how its configured to work with Office 365.

Prerequsities

An Office 365 administrator logon with permission to create a send connector.
Your internal domains must already be registered with us.
A Mimecast administrator logon with at view permission to the Gateway | Accepted Email menu item.

Mimecast recommend that if you are switching MX records, this task must be completed 3 days before changing the MX record to point at Mimecast. The reason for this allows Mimecast to build your Auto Allow list, based on recipients your users send messages to.

This has a positive impact on inbound email delivery speed, because many senders will already be known and consequently not be subject to our greylisting security feature.

Updating the SPF Record for your Domain(s)

You must have an SPF record for the domain(s) registered with Office 365. When implementing Mimecast with Office 365, this record must be updated in the DNS zone for the relevant domain to include the following:

Remove: v=spf1 include:spf.protection.outlook.com –all
Replace with or add: v=spf1 include:_netblocks.mimecast.com ~all

Important Note: If your outbound email is temporarily coexisting with Mimecast, you can leave the v=spf1 include:spf.protection.outlook.com –all SPF record. However, it must be removed once all your outbound email is routed through Mimecast.

Configuring Outbound Routing

Important Note: Mimecast has known issue with browsers that are not Internet Explorer and its recommend this process is completed using Internet Explorer only. All other browsers tested have issues.

Recommendation: Disable or remove any other Outbound Send Connectors. Failure to do this means your outbound email still uses these and isn’t routed through us.

Any send connectors used for other purposes (e.g archiving) may still be enabled. If in doubt, consult Mimecast Support.Any send connectors used for other purposes (login archiving) may login be enabled. If in doubt, consult Mimecast Support.

Adding the Office 365 Tenant Domain as an Internal Domain

Your Office 365 tenant domain must be added to the list of internal domains available in the Mimecast Administration Console. See the Configuring Internal Domain / Subdomains page for full details. This enables us to recognize certain auto response messages, where the sender address is not a normal internal domain. This is typically in the format @domain.onmicrosoft.com. Contact the Mimecast Support team if you have queries regarding this step.

Contact the Mimecast Support team if you have queries regarding this step.

Verifying Your Configuration

Once this step is complete, Office 365 must be added to your authorized outbounds as an umbrella account. View the Maintaining Authorized Outbound Addresses page for more information.

To verify that Office 365 is successfully routing email outbound via us:

Log on to the Offic 365 Administration Console.
Select Admin | Exchange

Select Mail Flow | Connectors
Create a Connector

Select Office 365 – From Field
Select Partner organization – To Field

Enter Name for Connector
Enter Description for Connector – Optional
Ensure “Turn it on” is ticked

Select “Only when email messages are sent to these domains”
Press the ( + )

Type the value * which will allow all outbound email to Mimecast

Press Next

Select “Route email through these smart hosts”
Press the ( + )

Now, depending on your location you will need to use the Smart Host address from the table

Region	Office 365 Account Hostnames
America	us-smtp-o365-outbound-1.mimecast.com
America	us-smtp-o365-outbound-2.mimecast.com
Australia	au-smtp-o365-outbound-1.mimecast.com
Australia	au-smtp-o365-outbound-2.mimecast.com
Europe (Excluding Germany)	eu-smtp-o365-outbound-1.mimecast.com
Europe (Excluding Germany)	eu-smtp-o365-outbound-2.mimecast.com
Germany	de-smtp-o365-outbound-1.mimecast.com
Germany	de-smtp-o365-outbound-2.mimecast.com
Offshore	je-smtp-o365-outbound-1.mimecast-offshore.com
Offshore	je-smtp-o365-outbound-2.mimecast-offshore.com
South Africa	za-smtp-o365-outbound-1.mimecast.co.za
South Africa	za-smtp-o365-outbound-2.mimecast.co.zaM

As shown below

Press Next

Select “Always use Transport Layer Security (TLS) to secure this connection (recommended)”
Select “Issued by a trusted certificate authority (CA)

Before pressing next please ensure that you confirm all your configured settings
Press Next

Press the ( + ) this will allow you to validate the connector

Enter an external email to send the test email

Click Validate

If everything is ok and configured correctly you should see a success message

Press save !!! and your all done

Recommendation: Disable or remove any other Outbound Send Connectors, if this is not completed it may cause email to fail as it won’t be routed through Mimecast

But if doing the above seems a bit boring, there’s always PowerShell 🙂

new-outboundconnector -name ConnectorName -smarthosts SmartHostAddress1,SmartHostAddress2 -tlssettings certificatevalidation -recipientdomains * -routeallmessagesviaonpremises $false -connectortype Partner -usemxrecord $false -whatif

or download my script for all Mimecast regions

Set-O365MimecastConnector (31 downloads)

Add your Office 365 domain as an internal domain in Mimecast

The Office 365 domain(s) must be added to the list of internal domain available in the Mimecast Administration console, if this action is missed. Mimecast are unable to recognise auto response message where the send address maybe @domain.onmicrosoft.com. Mimecast have a section about this on their website, please follow the link below.
Configuring Internal Domain / Subdomains

Verify your configuration

To verify that Office 365 is successfully routing email outbound via us:

Log on to the Administration Console.
Click on the Administration toolbar button.
Select the Message Center | Accepted Messages menu item.

See the Message Center: Accepted Messages page for full details.

You should see messages from your organization’s internal users to external recipients. If you don’t see messages shortly after they’re sent, this indicates a configuration problem on your Office 365 send connector. Double check your configuration. Use the Office 365 Message Trace Tool in the Mail Flow | Message Trace menu of the Exchange Admin Center to help identify the issue.

Important Note: Once this step is complete, Office 365 must be added to your authorized outbounds as an umbrella account. View the Maintaining Authorized Outbound Addresses page for more information.

Regards
The Author – Blogabout.Cloud

Get Disabled Users who have an Exchange Mailbox with PowerShell

By Author on April 1, 2019April 1, 2019Leave a Comment

If there’s one thing most IT department are not great at its removing Exchange Mailboxes for Disabled Users. So here’s a quick Powershell win to determine who within your Exchange organisation has a mailbox and a disabled AD account.

On-Premises Users


1
2
3
4
5
6
7
8
9
$Mailboxes = Get-Mailbox | where {$_.RecipientTypeDetails -eq 'UserMailbox'}

$Disabled = @()



Foreach ($Mailbox in $Mailboxes) {

    if((Get-ADUser -Identity $Mailbox.SamAccountName).Enabled -eq $False){

        $Disabled += Get-MailboxStatistics $Mailbox.SamAccountName | Select -Property DisplayName,TotalItemSize

    }    

}

$Disabled | Export-Csv -Path $env:userprofile\desktop\DisabledADUserwithMailbox.csv -NoTypeInformation

Cloud Users


1
2
3
4
5
6
7
8
9
10
11
Connect-MsolService

  

  $Mailboxes = Get-Mailbox | Where-Object {$_.RecipientTypeDetails -eq 'UserMailbox'}

  $Disabled = @()



  Foreach ($Mailbox in $Mailboxes) {

    if((Get-msolUser -userprincipalname $Mailbox.userprincipalname).Enabled -eq $False){

        $Disabled += Get-MailboxStatistics $Mailbox.userprincipalname | Select-Object -Property DisplayName,TotalItemSize

    }    

  }

  $Disabled | Export-Csv -Path $env:userprofile\desktop\DisabledAzureADUserwithMailbox.csv -NoTypeInformation

Regards

The Author – Blogabout.Cloud

Method invocation failed because [System.Management.Automation.PSObject] doesn’t contain a method named ‘op_Addition’.

By Author on April 1, 2019April 1, 2019Leave a Comment

While constructing a PowerShell script for gathering information about Distribution Lists within a customers environment, I ran into the following error

Method invocation failed because [System.Management.Automation.PSObject] doesn’t contain a method named ‘op_Addition’.

This error was being generated by a missing array within my PowerShell code


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
# Call Distribution Lists

$dist = @(Get-DistributionGroup -resultsize unlimited)



# Start Transcript

Start-Transcript -Path $env:USERPROFILE\desktop\DLsandMember.txt



# Report on Distribution List

foreach ($dl in $dist)

{

  

  $count =@(Get-DistributionGroup $dl.samaccountname).count

  $report = New-Object -TypeName PSObject

  $report | Add-Member -MemberType NoteProperty -Name 'Group Name' -Value $dl.Name

  $report | Add-Member -MemberType NoteProperty -Name 'samAccountname' -Value $dl.samaccountname

  $report | Add-Member -MemberType NoteProperty -Name 'Group Type' -Value $dl.grouptype

  $report | Add-Member -MemberType NoteProperty -Name 'DN' -Value $dl.distinguishedName

  $report | Add-Member -MemberType NoteProperty -Name 'Manager' -Value $dl.managedby

  $report | Add-Member -MemberType NoteProperty -Name 'Member Depart Restriction' -Value $dl.memberdepartrestriction

  $report | Add-Member -MemberType NoteProperty -Name 'Member Join Restriction' -Value $dl.memberjoinrestriction

  $report | Add-Member -MemberType NoteProperty -Name 'PrimarySMTPAddress' -Value $dl.primarysmtpaddress

  $report | Add-Member -MemberType NoteProperty -Name 'EmailAddress' -Value $dl.emailaddresses

  $report | Add-Member -MemberType NoteProperty -Name 'GrantSendOnBehalfto' -Value $dl.GrantSendOnBehalfto

  $report | Add-Member -MemberType NoteProperty -Name 'EmailAddressPolicyEnabled' -Value $dl.EmailAddressPolicyEnabled

  $report | Add-Member -MemberType NoteProperty -Name 'Number of Members' -Value $count

  Write-Host ('INFO: {0} has {1} members' -f $dl.name, ($count))

 

  $reportoutput += $report

}



# Stop Transcript

Stop-Transcript

By adding the following lines to my above script I was able to successful export the required information into an Array and dump out to CSV.


1
2
# Array

$reportoutput=@()

Regards

The Author – Blogabout.Cloud

PowerShell – ForEach do action X or do Y

By Author on March 28, 2019March 28, 2019Leave a Comment

PowerShell is one of the greatest tools within any IT Professional toolkit, it enables you to do far more than any GUI available to you today. In my life as a Consultant for a Global Microsoft SI (System Integrator), I face challenges every day where PowerShell has come to the rescue. One of the best cmdlet I use in a lot of script is

ForEach which is the alias name of ForEach-Object

Imagine you need to modify an ExtensionAttribute for your entire organization or grant a permission to a subset of users, ask yourself this? How would I do this in a GUI? and the answer would be “with great difficulty or very time consuming”. This is Foreach-Object comes into play, in the below example I need to modify the PrimarySMTPAddress due to special characters being used

In order to correct this, I will be using a source CSV file which contains SamAccountName for the identity of each DistributionList and the correct PrimarySMTPAddress.

Now for the most important element, the powershell script which will be used to modify the PrimarySMTPAddress. The below script has been designed to achieve the required outcome but also includes the ability to;

Be ran using native PowerShell for On-Premises Exchange Servers (2007 through to 2019)
Be ran against Exchange Online

So as we can see the Foreach command is being used in the following;

For each $row within the $csv which is being imported try and get the distribution list using the column heading SamAccountName
- If the Identity cannot be found the script will move to the catch
- If the Identity can be found the script will set the distribution list using the column heading PrimarySMTPAddress
The catch is alert if there are any unsuccessful attempts at setting the PrimarySMTPAddress

Simples!!

 Clear-Host
 $file = "$env:USERPROFILE\OneDrive\Desktop\groups.csv"
 $csv = import-csv -Path $file
 region Exchange Module SnapIn
 # Exchange 2007
   #Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin;
   # Exchange 2010
   #Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010;
   # Exchange 2013/2016
   #Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn;
 endregion
 Transcript
 Start-Transcript -Path $env:USERPROFILE\OneDrive\Desktop\Get-DistributionGroup.txt
 Foreach ($row in $csv)
 {
   try {
     Get-DistributionGroup -Identity $row.SamAccountName | Set-DistributionGroup -PrimarySmtpAddress $row.PrimarySmtpAddress
     Write-Host 'INFO:' ($row.SamAccountName),'Primary SMTP Address has now been modified to',($row.PrimarySmtpAddress) -BackgroundColor Green
   }
   catch
   {
     Write-Host 'ERROR:' ($row.SamAccountName),'Primary SMTP Address has not been modified to',($row.PrimarySmtpAddress) -BackgroundColor Red
   }
 }
 Stop-Transcript
 Get-DistributionGroup

I have included Start-Transcript as this will dump out all Write-Host entry whether they was successful or not.

Regards

The Author – Blogabout.Cloud

Goodbye OneNote 2016 from Office Portal

By Author on February 15, 2019February 18, 2019Leave a Comment

Back in September 2018, Microsoft announced it would be removing OneNote from its Office installation and OneNote for Windows 10 will be the default going forward. Microsoft has now announced (12th Feb) that OneNote 2016 will be removed from the Office Portal for installation using Semi-Annual channel.

So all installations from this post forward will not include OneNote 2016 by default when a user on the Semi-Annual channel using Office 365 on Windows 10 from the Office Portal.

So what now?

OneNote is available to download from the following url it is important to note that Microsoft are no longer developing new features for OneNote 2016. If you want to take advantage of the latest that OneNote has to offer, Microsoft state you should consider switching to OneNote for Windows 10

Regards
The Author – Blogabout.Cloud

Big News: Microsoft Teams being rolled out with Office 365 ProPlus (CDN)

By Author on February 11, 2019February 13, 2019Leave a Comment

Finally, Microsoft Teams will be introduce into Office 365 ProPlus… Microsoft Teams will be introduced into the;

February Monthly Channel; the
March Semi-Annual Channel Targeted (SAC-T); and
July Semi-Annual Channel (SAC)

But will automatically install Teams when Office 365 ProPlus is installed on new PCs and Macs.

Now the million dollar question, how is it being introduced?

As a Consultant that has delivered and spoke about Office ProPlus for a number of years, I do have concerns about how it’s going to be introduced and here’s why.

Office 365 uses the (CDN) Content Delivery Network for providing updates to all the Office ProPlus products, is it not the case with Microsoft Teams.

The update mechanism is completely different as the client is delivered by good old MSI so this will bring a number of questions and challenges to start;

What version of Office am I running?
What version of Teams am I running?
Does Teams need updating?
I have this weird problem but my colleague doesnt, is it version related?
etc.. etc…

However, if they integrate Microsoft Teams into the CDN it is definitely the way forward and also allows the customer to exclude Teams in the configuration.xml (if this is a requirement). It is very early days and I am sure more information will be released in due case but until then I am looking forward to see what the future holds as Microsoft have stated
“Teams will automatically be installed for users who already have Office 365 ProPlus in the future.” So if you’re not using Microsoft Teams today Microsoft are making damn sure its available to increase adoption.

The Author – Blogabout.Cloud

What about existing deployments of Office 365 ProPlus?

Updating Microsoft Teams !! It doesnt follow the normal ProPlus cycles.

Share this:

Baseline policy: End user protection (Preview)

Baseline policy: Block legacy authentication (Preview)

Baseline policy: Require MFA for Service Management (Preview)

Share this:

Share this:

What special characters are supported in Office 365?

Share this:

Prerequsities

Updating the SPF Record for your Domain(s)

Configuring Outbound Routing

Adding the Office 365 Tenant Domain as an Internal Domain

Verifying Your Configuration

Add your Office 365 domain as an internal domain in Mimecast

Verify your configuration

Share this:

On-Premises Users

Cloud Users

Share this:

Share this:

Share this:

So what now?

Share this:

Share this: