I am happy to be selected as a speaker for one of the biggest online conferences: Collab365. An event you can’t miss out on! This is one of the coolest conferences around, from the people organising it to the folks participating online. A single session can easily reach thousands of people, so you can imagine my excitement. Here are my session details:

Cloud Enabled Architecture: What to Consider & Keep in Mind !
Today, “Cloud” is part of our everyday life. I will share our experience of Cloud Enabled Architecture and discuss what to consider and keep in mind when you build Cloud Enabled Architecture! We will bring a lot of stories from the trenches, so you will see and hear the real information, not just information from official documentation!

You Will Learn:

• What is Cloud Enabled Architecture
• What to keep in mind
• What to consider
• Common mistakes and what we can learn from others

Click here to view the agenda. Hope to see you in the chat room for my session.

Many of us are using the HOSTS file for ages. However, not many people know about this “feature”.

So let’s see how it works. Often we use the hosts file to test new implementations, changes to an existing system and so on. During Office 365 implementations we need to have some C-Name record, so how do we test that by using just hosts files before we do any real DNS changes?

There are times when the deletion of a user account or a mailbox needs to be undone. It could be that we accidentally deleted the wrong user or maybe we are not really sure what happened to a mailbox, but want to attempt a recovery. Regardless of the reason, Microsoft has created a troubleshooter that will guide us to the best possible recovery option.

Planning an Exchange hybrid deployment.  This page has the support statement around what cross-premises permissions are supported (The below is from August 2016).

You should consider the following before you implement an Exchange Hybrid Deployment:

• Hybrid deployment requirements Before you configure a hybrid deployment, you need to make sure your on-premises organization meets all of the prerequisites required for a successful deployment. For more information, see Hybrid deployment prerequisites.
  Continue reading

During many Exchange projects (On-Premises or in the Cloud) we see a lot of situations when organisations create an additional mailbox (secondary mailbox) for some users. Everybody, who works with Exchange environments, knows that a mailbox could have multiple email addresses associated with it. The question is always, why not just define an additional email as an alias to the mailbox? Of course, this scenario could work in some use cases. You probably think, it’s OK…

However, when someone sends an email to the address that defined as an alias, the recipient is not going to easily see to what email address the email was sent (in more details down in this blog post). Also, when we only use aliases, all emails that we send are always seen as if they were sent from the primary email address associated with the mailbox.

We all know that  pictures explain better than 1000 words, so let’s take a look. Because of this, let’s see how to do this On-Premises and in the Cloud (Office 365).