Lync 2013 and Exchange Online UM – notes from the field

One of my recent posts was about Configuring Lync 2013 On-premises and Exchange Online to work together. After dealing with some feedback from customers and readers, I thought it might be worth to spend some time clarifying things: Edge Server You Edge Server must be configured as described in the post and enabled for federation. Confirm you have all the firewall rules in place between your Front-End and your Edge server, and your Edge server and the internet. Alternatively, you might want to restart your edge server or services just to be sure it’s all running… It’s all about the sequence There’s some logic in the order you’re committing the changes, especially if you’re migrating mailboxes from Exchange on-premises to Exchange Online. The steps are:

  1. Before you do anything, make sure the user is already in Office 365, synced using DirSync. If you’re migrating from Exchange On-Premises to Exchange Online, you’ll have to disable the existing UM option for these users. Don’t worry, all the data will still be there when you re-enable UM later.
  2. Run the Lync 2013 UM commands first. If the user is already synced or migration was completed, that’s the time to run the following: Grant-cshostedvoicemailpolicy –identity LocalDomain\<user> –policyname <PolicyName> and Set-csuser –identity LocalDomain\<user> –hostedvoicemail $true
  3. Let it sync. Although it should usually work immediately, go get a cup of coffee. Or something.
  4. Enable the user for UM in Exchange Online.

Just follow the steps… If you try to grant the on-prem policy to a user and you’re getting an error saying that the command cannot be found  – it means you probably missed or skipped one of the steps. The workaround is simple: Disable UM for that user in Office 365 and wait a while for the attributes to reset. then, run the Grant-cshostedvoicemailpolicy command and voilà- it’ll work.

Advertisements

Manually configure Outlook for Office 365 Exchange Online -Updated!-

As it appears, one of my most popular posts is “Manually configure Outlook for Office 365 Exchange Online” from August 2011. I wrote that when We were still suing the previous version of Office 365, and quite a lot has changed since.

This post will guide you on how to find the server settings for the latest Office 365 version, so you can manually configure Outlook to connect.

The host name for external access will always be outlook.office365.com.

That was the easy part. To find the ‘internal’ server’s name, we can use Microsoft’s Remote Connectivity Analyzer:

On the Remote Connectivity Analyzer page, choose “Office 365” and “Outlook Autodiscover”:

RCA_365_Autodiscover

Fill in your details on the next page and run the test.

On the test results page, start a search on the page and search for <Server>.

The first result will be a string saying something like <Server>f3e9173b-0bbe-4b20-b6db-4e8e739d8dbe@domain.com</Server>:

Server_Results

This is the address of your server. Copy and paste it, and that’s it:

Connected

Manually configure Outlook for Office 365 Exchange Online

Update:

You might want to check the updated version of this post HERE.

***          ***          ***          ***

For many reasons, you might want to manually configure Outlook to work with Office 365.

Here are some obstacles you may encounter:

  • You don’t have the Office 365 Sign-in assistant available.
  • No Autodiscover record published.
  • You’re working on Wndows Server 2003 and can’t install Office 2010 hotfix kb2544027. (If you want you can install only the .msp file, it skips all the prerequisites)

I tried following Microsoft’s Article about how to do it, no luck.

Finally, after doing some digging, here’s how to do it:

Log on to Office 365 OWA at https://outlook.com/<your.domain>:

Office365OWA Login

Once logged on, go to “Help, About”:

Office 365 OWA Help About

In the new window, look for “Host Name”:

Office 365 Help Host Name

Copy the the host name and close this window.

Now we can create a new profile in Outlook with the following configuration;

Choose to manually configure server settings:

then choose “Microsoft Exchange or compatible service”:

in the Server Settings window in the Server field, paste the name of the Host Name you copied earlier.

Now, for this to work correctly, you need to add the word “mailbox” betwin the Host name and the rest of the FQDN. So if my Host Name is “sinprd0602.outlook.com”, my Server name here should be “sinprd0602.mailbox.outlook.com”. Do the same for the name you copied:

Don’t forget to enter your Office 365 email address at the “User Name” field, then click “More Settings” and go to the “Connection” tab. Check the “Connect to Microsft Exchange using HTTP” box and click “Exchange Proxy Settings…”:

In the next window, fill the following details:

Type the Host Name you copied earlier in the “Use this URL to connect to my proxy server for Exchange” field.

Check the “Only connect to proxy server that have this principal name in their certificate” box and type: msstd:outlook.com.

Make sure both checkboxes are marked for connecting using HTTP first, and make sure you set the authentication method to “Basic”:

Click “OK” twice, then click “Check name” and enter your password at the prompt. the server and user names should be underlined:

Click “Next” and “Finish” and open Outlook, enter your password if prompted. That’s it, You’re connected!