Office365 (Exchange in cloud)


We recently migrated from an on premise Exchange 2003 server to Office 365 Exchange online plan P1.  A dirsync server (installed on Windows 2012 server) was installed in order to synchronize the AD structure with the cloud).

The environment consists of Windows 2003 Active directory.

Exchange 2003 system manager was installed on one of the domain controllers in order to manage the former on premise Exchange 2003 server.

Migrationwiz was used to migrate the on premise exchange system to the cloud.

I have the following questions concerning managing the new environment:

1. What is the default logon for office 365 ?  When I configured Outlook 2010 for integration with Office 365, the logon name is now the user's email address, where before it was the username. Is this expected behaviour or can it be configured to use the username instead of email address (in our 2003 AD structure, the value for  username is different from email address)
2. Does  a plugin like exchange system manager exist for managing Exchange in the cloud? For example, on the DC where exchange 2003 system manager is installed, there is an Exchange advance tab. On this tab I can hide the account from the global address book (for Exchange 2003). This option is available in Office365 portal. When I click in the office 365 portal to hide from global address book, the system saves I have to do so in the local AD structure. How can this be done?
3. Account creation- I have been told that when creating a new user, I need to create the user first through the office office 365 portal, assign an exchange license. Once complete I can then create the account in AD 2003. The account creation must be followed in this sequence in order to properly create a new user. These instructions seem odd. Is there not a better way to go about this? If I create the user in AD first, dirsync synchronizes with the cloud and the logon name is the username. One cannot access the email in the cloud.
4. Shared mailboxes - can either be set by logging into the outlook 2010 profile for specific account and granting access rights. The rights are then replicated to the cloud. There are options for directly managing these rights in the cloud, but they do not seem to have any effect

If someone can assist me with these questions, it would be greatly appreciated.

Thanks in advance.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vasil Michev (MVP)Commented:
1) It's the UPN, you can have it match the primary SMTP address, but that's not mandatory. You cannot simply user the username part (i.e. without the
2) When using dirsync, any object changes must be made in the AD first. The AD is the source of authority, and you cannot edit object that are synced. You can create objects directly in the cloud if needed
3) Creating users in AD is the right approach, dirsync will then provision the user in cloud and all you need is to assign a license. You need to however start using UPNs instead of username. So change to routable domain, add the suffix in AD if necessary, etc.
4) You can manage mailbox permissions via the EAC in Exchange Online or via EO PowerShell
mbudmanAuthor Commented:
OK - thank you for the information. I am not familiar with all the buzz words and I was not clear. I am aware that each user has to logon with ""

Let me clarify further - my question was can a person have the UPN (@company name)  instead of defaulting to the Primary SMTP address when creating (or in our case migrating users)? the UPN in our organization is the first letter of the employee's firstname+lastname, whereas the primary SMTP address is

Currently, when a user is created in Dirsync first, the logon name (for the cloud) defaults to UPN. How to I make it the primary SMPT address instead? (Originally I wanted UPN, but the consultant who did the migration did everyone with primary SMTP address; needles to say users were trying to login with UPN and it was failing).

Is there a way to change existing users logon name to UPN instead of Primary SMTP?

How does one make the connection to the cloud via PowerShell?


Vasil Michev (MVP)Commented:
You can change the UPN in local AD, the change *should* be synced to the cloud after the next dirsync cycle. In some cases I've seen this fail, but you can still change the UPN of the user via PowerShell using the following cmdlet:

Set-MsolUserPrincipalName -UserPrincipalName -NewUserPrincipalName

Open in new window

You will need the module for WAAD (the 'cloud AD'):

To connect to EO via PowerShell, check the steps in this article:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mbudmanAuthor Commented:
Thank you for your assistance.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Office 365

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.