Monday, 17 October 2016

Migration between two Office 365 tenants

In the era of cloud solutions, soon or later we will face the challenge of connecting two of them together. Merges and acquisitions of companies which possess separate cloud IT infrastructure needs to be joined, unified and also simplified if possible.
Using experience after few successful migrations, I will try to explain here the most important things to consider in similar projects, when Office356 is involved.
This is not step by step instruction – only lessons learned from the migration field.
At the beginning - things which appears every time you plan a change in the organization.

Determine customer expectations and goals

The most important thing, which – when chasing for time and money some people forget - the success of the project depends on the fulfilment of customer expectations. Dot.

More you can read at the Gooroo site:

Friday, 4 March 2016

550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this organization

Did you encounter a problem when you are trying to set message size in the organization, but still get the 550 5.2.3 error?
This is tricky, because on the transport level you need to set the same for both - Receive i Send size.

Set-TransportConfig  -MaxReceiveSize 50MB -MaxSendSize 50MB

Sunday, 8 November 2015

Exchange 2013/2016: Cannot set AD-RMS rule - no RMS template

If you are trying to set your AD-RMS integration with Exchange, after followin all of the required steps to install and turn on AD-RMS, you probably will need to create transport rule in order to automatically secure e-mails.
If everyting is OK, then you should see default template "Do not forward" and others already configured with AD RMS.
But when I've tried to set the rule, the rule list was empty:
I've checked RMS templates and configuration with powershell:

As you see there is no template in this configuration and local SQL server is not accessible.
You should check if internal SQL database or SQL server (depends on your config) is accessible.
In my test environment, MSSQL$MICROSOFT##WID service was down. After starting it, RMS templates shown up.

And now, I was able to create RMS rule in the transport rules with RMS template.

Tuesday, 7 April 2015

Outlook2013: Cannot see online archive

Dear Administrator, my archive online is not visible in the Outlook - said CEO...
Did you hear that maybe?
I have simple answer for you - DON'T buy OEM versions of Office products.
Archive Online feature needs volume license to work in most cases?
Don't believe me?
Check this out:

Friday, 5 September 2014

Office365: Limiting access to Office 365 using ADFS

If you need to restrict access to Office365 for users outside your company at all or just for group of them then you need to use ADFS servers.

When you have set them properly and you can be authenticated by ADFS, then you can configure ADFS claims to restrict the Office 365 access.

First, I've tried use the solution provided in this link:

But, this not work in my environment.

I've been looking for article below, but can't find it as "limiting access".
Then when asked Microsoft they give me the right link.

Here is the right link:

Office365: Add new licence / subscription key to the tenant


Today easy and short tip, but you could wander around for hours searching this:
When you have bought new licences you can easily add key to the subscription.

Go to the Volume Licencing Center at:
(If you have not logged in earlier here you need to register with e-mail account provided with licence order)

Get (copy) your subscription key from the license.

Next go to this link:
and paste the key.

That's all!

If you have used trial licences you'll have to change your user's licences from trials to the new one.

Monday, 2 June 2014

Office365: Cannot move, migrate mailbox. The operation couldn't be performed because object couldn't be found on...

The operation couldn't be performed because object couldn't be found on...

This error appears when you try to move (migrate) mailbox from on premises Exchange to the Office365. It means that object with same date exists in both sides and it differs in some way.
It could happen if you have created mailbox in Office365 without migration from on premises Exchange.
To resolve this issue, you need to remove user from Office365 side and synchronize it again and then migrate mailbox to the cloud.

So, connect to Office365 from Powershell.
Then run:
Remove-MsolUser -UserPrincipalName

Next, run:
Remove-MsolUser -UserPrincipalName -RemoveFromRecycleBin

Now, wait for dirsync replication or force it and you should have the ability to move the mailbox to Office365 from onprem Exchange.