Forum Discussion
Azure Connect (Azure Advisors) and other Yammer Community 403 Freemium Errors
Hello, this happened once before a year ago, but slightly different error. None of my colleagues can access the Azure Connect private external community if they are based in UK, possibly Europe. We just get an instant "fail 403 blocked_freemium_user" error. Our internal IT say we have E5 licensing ,which allows external network use and they have made no changes to block any traffic. Not getting any traction on searches around topic other than it referring to older articles about deprecate licensing relating to using external Yammer communities.
I was wondering if any Yammer admins are picking up on this type of error on external Microsoft communities.
Update: Now getting fail 42 blocked_freemium_user error instead.
7 Replies
- Hi,
I'm having the same problem. Where can I raise a ticket?- Microsoft Support through your tenant. Although we are still not anywhere near resolving it and keep getting pushed back saying engineering teams are busy.
- I am now working again after having my Freemium identity deleted and reapplying for membership to the the external community.
DamianReffin when will this be solved? I still get the error fail 42 blocked_freemium_user when trying to access Azure Advisors
- If the issue is the same as ours, you will need to get a Microsoft ticket logged to find out if you have a US GEO Yammer instance that is causing your issue and get it retired/deleted.
DamianReffin Hola, tengo el mismo problema solo al querer consultar unos mensajes privados, ¿pudiste solucionarlo?
- I have posted the answer as far I have managed to take it with Microsoft support. A legacy Yammer network in US GEO with Freemium users is the likely cause. We are working on getting it deleted by support.
