Cloud Hub

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: July 7, 2021

General information

Information provided by atwork GmbH to Microsoft:

Information Response
App name Cloud Hub
ID WA200003034
Office 365 clients supported Microsoft Teams
Partner company name atwork GmbH
URL of partner website
URL of Teams application info page
URL of Privacy Policy
URL of Terms of Use


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

How the app handles data

This information has been provided by atwork GmbH 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
Channel.ReadBasic.All application Read the names and description of all channels Nothing b5d4e933-e001-4168-83f8-abdd974877bd
Mail.Send application Share a message to a Microsoft Teams team via E-Mail. Nothing b5d4e933-e001-4168-83f8-abdd974877bd
TeamSettings.Read.All application Used for sharing within a Microsoft Teams team. Nothing b5d4e933-e001-4168-83f8-abdd974877bd
User.Read delegated Sign in and read user profile Nothing b5d4e933-e001-4168-83f8-abdd974877bd
User.Read.All application Used for people picker for sharing messages. Nothing b5d4e933-e001-4168-83f8-abdd974877bd

Data access using other Microsoft APIs

Apps and add-ins built on Microsoft 365 may use additional Microsoft APIs other than Microsoft Graph to collect or process organizational identifiable information (OII). List any Microsoft APIs other than Microsoft Graph this app uses.

API Is OII collected? What OII is Collected? Justification for collecting OII? Is OII stored? Justification for storing OII?
Office 365 Management APIs Yes ActivityFeed.Read and ServiceHealth.Read Make activity feed and service health available for non-admin users ActivityFeed and ServiceHealth Data To optimize the performance

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.

Data access via bots

If this app contains a bot or a messaging extension, it can access end-user identifiable information (EUII): the roster (first name, last name, display name, email address) of any team member in a team or chat it's added to. Does this app make use of this capability?

No EUII is accessed.

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?

No OII or EUII appear in the applications telemetry or logs.

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.

The app reads data and stores it in a customer data storage, which is provided as SaaS. Additionally, users have the posibility to send messages as mails or send them into groups.

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?



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

Identity information

This information has been provided by atwork GmbH 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 Multi Tenant app, depends on the customer´s settings
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
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? No
Does your app use deprecated APIs? No


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