Has anyone managed to create a Teams application?
I’m getting account@domain does not have a valid license, please assign valid Office 365 license to the user when creating the app after is has gone through the authorize step. The screen for the last step also shows “An error occurred while acquiring the token.”
The account I’m using is a global admin and has a basic O365 license. I can log in and send/receive mails so it is licensed. BoL is severely lacking on content on how to create an Office 365 Teams app in Command Center but what is there shows the requirements which we seem to have met. We’re running CV 11.22.18.
Best answer by Mike London UKView original
@Mike London UK , appreciate the message!
I’m having the same trouble finding it in our documentation.
Let me speak to some internal folks and get a definitive answer AND get the docs updated.
I heard back from one of our engineers that we need a license which has "teams service component" enabled in it. Can you log onto the o365 admin portal and ensure the used account has that license?
I’ll engage our documentation team to get this updated clearly.
I did want to add that the 11.23 docs on Teams are much better than the 11.20 one:
What kind of Office 365 license is does the user have?
We need a user assigned with an Office 365 plan which has “Teams service” enabled.
I did look at FR22 and FR23 docs but was looking at Expert option (I really hate this new BoL segregated layout).
I’ll report back if I find what’s required to be be changed.
Understood on BOL. It’s a semi new breakout (the Expert parts are only for customers in Maintenance) so if you see anything amiss, click the little feedback button and our documentation team will tighten it up.
I gave a quick look on the various license types and can see that Basic is the entry tier, so I expect it lacks the Teams Service:
Here’s a doc on the Teams Service:
Clicking the License Requirements/find what’s right for you doesn’t really answer either:
Curious to see what your Azure people can share. I’ll keep an eye on your reply.
From my reading of the linked docs, “Teams Service Component” just means Teams (like Exchange and SharePoint). That being the case the account we’re using has that component. It is able to log in to the Office portal and can run Teams successfully.
Let me know once you do and send me the case number so I can track the resolution.
@Mike Struening I have just raised 210419-273 for this issue.
I have the same issue. I am using the global admin for my metallic test account and for my commvault environment. In metallic the global admin works but not in the commvault env.
@Mike London UK ! I’ll keep an eye on the case and share the solution back here (assuming you don’t beat me to it)!
Please review below
-Check license details from the O365 portal and check if it has E3 license for the Service account which is used for configuration.
-Check and make sure that the account has an Active Mailbox in Exchange Online
-Check the .NET framework version installed on the Web Server:
-Make sure that .NET version is 4.7.03062 or higher
We installed .NET Framework 4.7.03062 on our Commserve (web server) as well as 11.22.19 (from 11.22.18). I assume it’s the .NET FW change that has sorted the issue. We did not need to allocate an E3 license.
The account must be a global admin and have an active mailbox
I installed .net 4.7 and now everything works as expected. thanks for your help :)