Let’s discuss Microsoft Import Service Office 365! Last time, we went through E-Mail migration using a third party tool: Dell On-Demand Migration. Check that instead if Microsoft Import Service is not sufficient for your needs.
In some scenarios though, you’re better fit using the Import service Office 365. This is a great tool delivered last year by Microsoft. This step by step guide is intended to help you upload your PSTs to Office 365 and import them to your user-mailboxes. Let’s start!
The step by step Office 365 to Office 365 migration guide is up. This isn’t as straightforward as one’d wish. When you first register a domain to an Azure Tenant, you cannot register it in another Tenant. This is understandable from a logical standpoint, but who better than Microsoft to make tools for you to easily move to a new tenant? Apparently, even Microsoft advises you to use third party tools.
As stated in the article, there are some steps, and there will be downtime. Not long downtime, but be sure to be prepared.
Designing Azure AD can be complex if we’re leaving local AD. We need to make sure we have naming conventions in order. What about our devices like printers, where will they go? Here we will go through the designing phase of our series.
As my first post I’d like to explain who I am, and what my intentions are for this blog.
I’m a Senior Cloud Deployment Consultant currently employed at Crayon. My areas of expertise are SaaS such as Office 365, Intune, Azure AD, IBM MobileFirst and VMware Airwatch.
Setting these up by themselves is not hard at all, we could all start a new Microsoft tenant (something.onmicrosoft.com) in mere seconds. No, the real challenge starts when you try creating hybrid-solutions, or want to migrate lots of data from one place to another.
I’ve been longing for quite some time to write my own findings, guides and how I solve the problems I experience.