I would love to get more information reagrding this integration? We are starting to use Microsoft Teams in our environment.
The engineering team has just pushed out an update with this fix. Please refresh your browser if you are using the Teams web app, or quit and reopen the Teams desktop client in order to see the updates. No need to delete/reinstall the app.
Still to come is a bot message that will help bring to light any unmet pre-requisite steps that need to be completed before the bot can generate a meeting link.
Hi James, I'll reach out soon to schedule a quick call.
Would you be able to arrange a call for me also?
I've gotten several requests to schedule calls to discuss our Microsoft Teams integration, which is very exciting.
I've set up an online calendar to streamline the scheduling process. If you'd like to join a call to learn more about our Microsoft Teams integration, please select a time here: Calendly - Whitney Doyle
Hopefully I'll be talking with you over Lifesize soon!-Whitney
Following this procedure,
the bots don't work.
the application is published with O365 tenant admin.
I can see the application.
I added the application on a teams channel
I create a post with
But no popup with link or whatever.
Do you have an idea ?
Exactly the same happening for me. If you get a fix please let me know. I have logged a support ticket though.
Same issue here. Bot doesn't respond.
Same goes to me.
I have been working with Lifesize Support on the Teams bot not working. We have got to the stage that the Bot does create the Meeting room when you do @Lifesize start. It just does not come back and give you the details of the room in the Teams bot. They are aware of my problem and I am awaiting an update.
Same happen to me . I did see the room created on LS cloud but don't have the call details in Teams
Please note that the one time meeting option is required on the Lifesize cloud account for Teams integration. Your local Lifesize representative would be able to enable a 14 day trial of one time meetings.
Kevin, Ivan and I have the same issue and I know I have the trial enabled as that was the first thing I asked for. So it is another issue.
Jeff, I can see from the support case notes that one time meetings have been enabled for your account but did not see the same for Ivan which is why I replied to his post. When was your last communication with Lifesize support? It appears they have been reaching out via email and we wanted to make sure those messages were not stuck in your spam folder, thanks.
The last message I had from Brandon Jones was two days ago.
The video made it crystal clear. Let me research this.
As I sent him a video of what was happening.
my Lifesize cloud account able to create one time meeting. I can create one time meeting using my lifesize cloud app.
I already authorized for the permission.
The ticket i opened was handle by Brandon as well.
Just check my Lifesize account and I too can see the OTM's being crested but like you the bot is bringing nothing back in to Teams. Would be good to know what you get back from Lifesize as I still have a support ticket open with them also but it's only just now I have realised OTM's are being created when logging into the Dashboard
I appreciate you all taking time and discussing this on community.
I would like to let you know that we have escalated this issue to our engineering team and we are looking into this further. Once we have the feedback from them we will further update you.
Meanwhile, with initial integration with Microsoft team if you encounter the issue again where Bot is not responding, please checklist below points:
1. OTM (One Time meeting) is enabled on the account.
2. If yes, please browse to below URL and check if lifesize app has permission in Microsoft teams:
3. If not, please authorise the permissions.
4.Logout from teams and sign-in again.
If it still does not work, please submit a case here with email address using which you logged into Microsoft teams and the time at which the issue occurred.
Global Support Engineer, Lifesize.
Thanks you for your message.
I tried the link, not work also :
I tried to authorize the application directly from Azure AD, but...
The application needs a lots of rights !
Particulary in Exchange mailbox users !
At this time it's impossible for me to grant the application on my tenant.
Why Lifesize needs to have access to Exchange mailbox ?
Great question. We investigated what Exchange permissions we absolutely needed for our integration and only ask for what is required in order to provide you and your users with a valuable experience. Just as we handle your video communications, rest assured we take your communication security very seriously and hold our integrations to the same high standard as our video and audio communication clients.
Our integration requires the highlighted permission in order to provide the following value: 1. When users schedule a meeting in the Teams app, we need Exchange permission to automatically add a Lifesize meeting link to the meeting description details, so your users do not have to manually perform this action every time they want to schedule a Lifesize meeting. 2. When users schedule a meeting in the Teams app, Microsoft always adds a link to join via a Microsoft Teams call, which can cause a lot of confusion for invited participants who see conflicting ways to call in their meeting descriptions. To reduce the confusion, our app removes the Microsoft call-in link from invitations that our intended to be Lifesize hosted meetings.
Thanks for your reply.
I'm ok for Caldendar rights, and API graph is used for that. (see my first capture)
But why needed to access to the entire mailboxs ?
We started off using the Graph API approach in our early development stages, but found that EWS is a much better implementation for our customers, because it is far less invasive and allows our bot to interact much faster.
To explain further: If we used Graph API today, we would need to access every Teams' mailbox, and routinely pull and search through ALL of its contents in search of changes related to Lifesize, which would mean retrieving and sifting through content that is not relevant to our Lifesize integration. That would slow down our bot significantly, and pose unnecessary security risks. By using EWS, we do not have to programmatically retrieve and search through all mailbox content. Instead, our services subscribe to be notified only when there are changes relevant to Lifesize. In this way, our bot is able to perform more efficiently and is only involved with your Team mailboxes when it is absolutely relevant to Lifesize.
The text for the required permission level is misleading, as it implies we are accessing all mailboxes in your organization, but our integration only subscribes to changes relevant to Lifesize for Microsft Teams' Team mailboxes—not individual users’ mailboxes. Hope that helps clarify our permissions and why we chose the EWS approach rather than Graph API.
All the best, Whitney
The fix works for me, good job.
The update fixed the issue. Everything works now.
Retrieving data ...