03-06-2013 10:46 PM
According to Microsoft, their new Midsize Business plan is supposed to include BBCS. I have signed up for the plan trial and the option to enable BBCS is available, but when attempting to manage the service I receive the following after being redirected to RIM BBCS page:
Tenant authorization error
You do not have a Microsoft® Office 365 plan that allows you to register a tenant. You must upgrade to a plan that includes an enterprise exchange subscription. Please contact Microsoft® Office 365 support.
I've removed and re-enabled the service several times, waited days in between attempts, same result. I have contacted MS support and they, of course, tell me to contact RIM support. Anybody else seeing this same behavior?
03-12-2013 10:00 AM
Having the exact same issue here - Midsize Business Plan, got BBCS activated but getting "Tenant Authorization Error" when trying to manage it.
This has been going for several weeks now (I registered on 27th Feb - the day the new packages got announced).
I've been constantly in touch with Microsoft's support and also got forwarded to RIM's support once but no avail.
This is starting to get really annoying (especially as BBCS was the only reason I chose this package) so I would highly appreciate if someone could comment on this.
03-12-2013 03:44 PM
i hear about it's MS. They don't want to install BES10 on exchange server...and without BES 10, you can connect to the BBCS. I believe is the reason why we got this error.
so in don't think i will buy this package....with hope the situation change.
03-15-2013 10:55 AM
Got a small update here:
After spending another half hour on the phone with Microsoft (and they called RIM while I was holding the line) they finally admitted that the problem is indeed on their end, and it's apparently being looked into by their engineers. They said they would update me once there's any progress but couldn't give me a time frame.
03-19-2013 07:08 AM
As of this morning (19th March) everything seems to be working!
So anybody following this thread - give it another go. I also read from someplace else that the issue got resolved (yet ironically no reply from Microsoft who were supposed to "let me know as soon as anything changes" lol) so I'm not the only one.