Monthly Archives: April 2012

Configuring External Communications In Lync Online (Office 365)

The title might confuse you, as many of you might have heard that everything is setup correctly in Office 365. I found that the external communications was disabled for my tenant for some reason.

While checking out the settings for Lync Online, I found the status for external communications to be Enabled, but the status was listed as disabled for all my domains, including the one.

Disabled by default

In order to fix it, I had to disable the external communications using the Disable button. That changed all my domain status to Connection Pending.

External Comms pending

It took more than a day for me to get all my domains enabled for external communications.

External Comms enabled finally

Next time you play with Office 365, check all the settings. Don’t just assume that everything is setup correctly & will work out of the box Winking smile. I learned this the hard way while setting up my on-premise Lync to federate with Lync Online, covered here. I was troubleshooting the on-premise deployment, while the problem was clearly with the Office 365 setting!

Enable Lync On-Premise To Federate With Lync Online (Office 365)

One of the selling features of Lync 2010 is the ability to communicate with users outside your organization – be it a remote user, federated or PIC. How can we communicate with a company who has Office 365 subscription?

Lync 2010 doesn’t allow communication with Lync Online (Office 365) out of the box. You need to add a provider for Lync Online for the communication to work. Let me explain.

I have an Office 365 subscription with a Lync user My on-premise Lync has an account I want my on-premise Lync deployment to communicate with Office 365. How can I do it?

Launch Lync Control Panel and navigate to External User Access –> Provider. There are only three provders by default.

Default providers

We need to create a new provider for Lync Online. Hit the New button and create a new Hosted Provider. Give LyncOnline as the name of the provider and as the access edge fqdn. Select Allow all communications with this provider, unless you want something granular. Hit the Commit button.

Create provider for LyncOnline

Make sure that the new provider is enabled.

Lync Online Provider Enabled

That’s it. If you are into PowerShell, open up Lync Shell and run the following command to achieve the same result.

New-CSHostingProvider –identity LyncOnline –ProxyFqdn –Enabled $True

You should now be able to add the Office 365 user in your on-premise Lync client and the presence will be updated immediately & you can chat straightaway (provided that you have enabled external communications, covered here).

Onpremise Lync client

Sure enough, the Office 365 side (OWA and Lync client) picks up the on-premise presence as well.

Office 365 client

Pretty good Winking smile