UPDATE: The article was written with limited context I have from Microsoft notification in my email. What I have learned is that it wasn’t Microsoft’s decision but AOL’s to stop connecting to Microsoft’s PIC clearninghouse! Either way, the spirit of article stays the same. Special thanks to Keith Hanna for pointing out facts and add context to this information.

For those of you who use Microsot Lync server’s Public IM Connectivity (PIC) to connect your users with AIM, it’s time to take notice. Microsoft announced today in an email to PIC users that they will no longer accept new requests for Aim federation through PIC service.

What has changed?

Effective immediately, Microsoft will no longer allow you to provision your domains. Existing AIM connectivity is not affected and will continue functioning through June 30, 2014.

What do you need to do?

If you are current AIM federation user, you need to plan transition. Your AIM connectivity through PIC will continue working until June 30, 2014. In the meantime, Microsoft is advising administrators to contact AOL directly through AOL’s dedicated portal and start utilizing substitute service offered directly by AOL. You can find details here: http://aimenterprise.aol.com/pic.php.

If you do not use AIM connectivity through Microsoft’s PIC offering but are planning to use it in near future, you need to contact AOL directly and utilize substitute service offered by AOL instead. You can find details here: http://aimenterprise.aol.com/pic.php.

And if you are one of those who are existing AIM connectivity users through PIC but can’t wait to get rid of that service, you need to do nothing. Stay put and on June 30, 2014 you will be able to send one last IM to AIM before Microsoft turns off that connectivity.

Quick question, how many of you are really using AIM connectivity? The last recollection I have of AOL is those floppies I couldn’t seem to get away from.