Forum Discussion
Display online status next to name in Outlook Greyed Out
It is not effecting all users which was/is the aggravating part
Installed but did not login to skype for business Free/Busy Jellybeans in Outlook showed up but did not sync
Changed
Computer\HKEY_CURRENT_USER\Software\IM Providers
Changed DefaultIMAPP Value to Teams
Fixed :) Bit of a cheap and nasty fix but it will do until hopefully next update that will address this issues
DannyVLRS Please try to use New Team app, and your issue will be resolve.
Start using the new Teams- Open the Teams desktop app on your Windows device.
- Turn on the Try the new Teams toggle at the top of Teams.
- Select Get it now from the pop-out dialogue. The new Teams will start installing.
- Your Teams app will reboot to open the new Teams.
You can go to file > options > addins > Go
Check microsoft teams / skype has a check mark or not
If not click, check that option and click on okay
Close outlook and re-open
Once it is re-open check
then you will have the option to check
If not then you have to add the addin
Basically your outlook needs to be synchronized with teams/ Skype, Thats when Display online status next to name will be available.
- I follow the step but cannot see the changes. Its same.
DannyVLRS - still a bug for us. I've noted that users are unable to change this as greyed out and ticked. Myself as an admin could change but after changing the Teams setting mentioned previous and closing both outlook and teams and reopening both the option is then greyed out for myself.
Eventually i noted the setting returned and i could tick and untick.
I wonder if its a Teams tenant thing causing this..?
Gary Smith Hi there!
Our experience was this was client side. Office 365 Pro Plus (now M365 Apps for enterprise) had Skype for Business (S4B) in it. If you did not install S4B, the presence between Teams and O365 was missing. It was actually S4B that did it. Teams at the time did not have the code to do it. We hit the issue on new SOE PCs when we decided to drop S4B.
A workaround was to re-install S4B but not an ongoing solution.
Time went by and Teams was developed further by Microsoft and the workaround is no longer required. Teams has its own code to work with O365 / M365.
For you, ensure Teams is updated and M365 is also in service.
It looks like Microsoft finally fixed the problem. I got an update today. Office ProPlus Montly Channel (Targeted Release) 2003 (Built 12624.20176)
RonaldvdMeerand to All,
I understand this was solved with a Teams update. See issue #4454
https://docs.microsoft.com/en-us/microsoftteams/presence-admins
Enjoy!twhere is the fix this is just telling us what it is
No that is not the solution. Please read the complete thread before commenting with useless solutions. This wil only work if Skype for Business is still installed.
Just found a way as a workaround to solve this issue. I've tested it on my environment: Windows 10 1809 & Office 365 64 bit & Teams, it's working fine.
My steps:
1. Install the Skype for Business. Not need to login, just install it.
2. Modify the registry - 'Computer\HKEY_CURRENT_USER\Software\IM Providers\Communicator', empty every keys, except the 'Default'.
3. Maybe need to reboot.
Then the presence icon will be working fine.Anyway, this just a workaround for me, cause I have to install the Skype for Business, even I didn't need it. And I guess Microsoft is still working on fix this issue.
Reference link:
https://docs.microsoft.com/en-us/microsoftteams/presence-admins- These Steps are working Thanks.
No they don't. This probably only will work if Skype for Business is installed.
So this is not the solution.
I have found a solution that worked for me.
HKEY_CURRENT_USER => SOFTWARE => IM Providers. Verify that DefaultIMAPP is set to “Lync”
For more details check that link: https://khushsolanki.blogspot.com/2017/07/fix-skype-for-business-integration-with.html
- what version/channel of Office are you on there?
Office 365 MSO 16.0.10730.20348 64 bitDon Pickard
DannyVLRS >> Office 365 MSO 16.0.10730.20348 64 bit
Ok so that's v1808, the same version we're using, which is impacted, but as below, v1902 also impacted
