Luware Nimbus for Microsoft Teams

Publisher Attestation: The information on this page is based on a self-assessment report provided by the app developer on the security, compliance, and data handling practices followed by this app. Microsoft makes no guarantees regarding the accuracy of the information.

Last updated by the developer on: October 1, 2021

General information

Information provided by Luware AG to Microsoft:

Information Response
App name Luware Nimbus for Microsoft Teams
ID luwareagzurich.advanced_routing_azure_marketplace
Partner company name Luware AG
URL of partner website https://luware.com
URL of Privacy Policy https://luware.com/en/privacy-policy
URL of Terms of Use https://luware.com/en/agreements/saas/

Feedback

Questions or updates to any of the information you see here? Contact us!

How the app handles data

This information has been provided by Luware AG about how this app collects and stores organizational data and the control that your organization will have over the data the app collects.

Data access using Microsoft Graph

List any Microsoft Graph permissions this app requires.

Permission Type of permission (Delegated/ Application) Is data collected? Justification for collecting it? Is data stored? Justification for storing it? Azure AD App ID
Calendars.Read delegated Attendant Console: Read Calendar of the logged-in user show Calendar with appointments None 23694b6c-5a4a-45ce-9c6a-37c5f1880d4e
Calendars.Read.Shared delegated Attendant Console: Read Shared Calendars to show Calendar with appointments None 23694b6c-5a4a-45ce-9c6a-37c5f1880d4e
Contacts.Read delegated Attendant Console: Search in the Exchange Contacts of the logged-in user None 23694b6c-5a4a-45ce-9c6a-37c5f1880d4e
Contacts.Read.Shared delegated Attendant Console: Search in the Shared Exchange Contacts None 23694b6c-5a4a-45ce-9c6a-37c5f1880d4e
GroupMember.Read.All application Get Team Members, Read Security Groups We store this information as call center agents are managed through group memberships 23694b6c-5a4a-45ce-9c6a-37c5f1880d4e
Presence.Read.All delegated Show Presence in Contact Search on Attendant Console page None 23694b6c-5a4a-45ce-9c6a-37c5f1880d4e
User.Read delegated Get UserInformation (from logged in user) None 23694b6c-5a4a-45ce-9c6a-37c5f1880d4e
User.Read.All both Nimbus App - Get CallerInformation. On an internal call to the contact Center we do a reverse lookup on who it could be so we can show that information to the Agent. In the Attendant Console (with delegated permission) we search the whole internal directory for transfer targets. For Reporting REasons on who called the most, we store that data. 23694b6c-5a4a-45ce-9c6a-37c5f1880d4e
User.ReadBasic.All delegated Limited User Search None 23694b6c-5a4a-45ce-9c6a-37c5f1880d4e
Calls.AccessMedia.All application Many of those Apps/Bots (One per Contact Center Queue): Subscribe to DTMF tones where the customer actually can select his position in the IVR All DTMF Info for selected ways through the IVR for Reporting reason 7e1fc6b3-90a7-4a98-a766-5627193e95bc
Calls.Initiate.All application Many of those Apps/Bots (One per Contact Center Queue): Make call to Agent All CDR Info for Reporting reason 7e1fc6b3-90a7-4a98-a766-5627193e95bc
Calls.InitiateGroupCall.All application Many of those Apps/Bots (One per Contact Center Queue): Make call to Agent All CDR Info for Reporting reason 7e1fc6b3-90a7-4a98-a766-5627193e95bc
Calls.JoinGroupCall.All application Many of those Apps/Bots (One per Contact Center Queue): Join an escalated call to play announcements All CDR Info for Reporting reason 7e1fc6b3-90a7-4a98-a766-5627193e95bc

Non-Microsoft services used

If the app transfers or shares organizational data with non-Microsoft service, list the non-Microsoft service the app uses, what data is transferred, and include a justification for why the app needs to transfer this information.

Non-Microsoft services are not used.

Telemetry data

Does any organizational identifiable information (OII) or end-user identifiable information (EUII) appear in this application's telemetry or logs? If yes, describe what data is stored and what are the retention and removal policies?

Aggregated reporting Data (Call Detail Records, caller information, call treatment and call journey details etc.): 24 months Configuration Data: Customer Contract duration +30 days Application logs: Temporary storage of internal application logs (to help our support engineers troubleshoot the performance and operation of application components) 30 days.

Organizational controls for data stored by partner

Describe how organization's administrators can control their information in partner systems? e.g. deletion, retention, auditing, archiving, end-user policy, etc.

https://luware.com/en/privacy-policy/

Human review of organizational information

Are humans involved in reviewing or analyzing any organizational identifiable information (OII) data that is collected or stored by this app?

Yes

Feedback

Questions or updates to any of the information you see here? Contact us!

Identity information

This information has been provided by Luware AG about how this app handles authentication, authorization, application registration best practices, and other Identity criteria.

Information Response
Do you integrate with Microsoft Identify Platform (Azure AD)? Yes
Have you reviewed and complied with all applicable best practices outlined in the Microsoft identity platform integration checklist? Yes
Does your app use MSAL (Microsoft Authentication Library) for authentication? Yes
Does your app support Conditional Access policies? Yes
List the types of policies supported Client apps, Users and Groups
Does your app request least privilege permissions for your scenario? Yes
Does your app's statically registered permissions accurately reflect the permissions your app will request dynamically and incrementally? Yes
Does your app support multi-tenancy? Yes
Does your app have a confidential client? Yes
Do you own all of the redirect Unified Resource Identifier (URI) registered for your app? Yes
For your app, what do you avoid using? - Wildcard redirect URIs,
- OAuth2 Implicit Flow, unless required for a SPA
- Resource Owner Password Credential (ROPC) flow
Does your app expose any web APIs? Yes
Does your permission model only allow calls to succeed if the client app receives the proper consent? Yes
Does your app use preview APIs? Yes
Does your app use deprecated APIs? No

Feedback

Questions or updates to any of the information you see here? Contact us!