> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/attendant-console/compliance-and-reference/compliance-and-technical-reference.md).
# Attendant Console for Microsoft Teams compliance and support
Review compliance, data handling, regional availability, permissions, and support boundaries for Attendant Console for Microsoft Teams.
{% hint style="warning" %}
Attendant Console for Microsoft Teams is in End of Sale. Existing customers can continue to use the product and receive support. License renewal remains available until December 31, 2026.
{% endhint %}
Use this page to review compliance-related information, data handling, permissions, and support considerations for Attendant Console for Microsoft Teams.
The product-track overview owns the canonical definitions and technical operating boundaries. This page is the support and compliance route.
{% content-ref url="/pages/m3gECKKOstNeijLHkqNE" %}
[Attendant Console for Microsoft Teams technical reference](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md)
{% endcontent-ref %}
{% hint style="info" %}
This page is not a legal document. It provides an overview of architecture and compliance-related policies for Attendant Console for Microsoft Teams.
{% endhint %}
## SaaS platform architecture
Attendant Console for Microsoft Teams runs on a modern, multi-tenant SaaS platform hosted in Microsoft Azure.
Service map for Attendant Console for Microsoft Teams.
### Authentication
The platform uses the standard Microsoft authentication mechanism. Authentication is handled by and hosted by Microsoft, so AnywhereNow does not have access to user credentials.
When the Microsoft Teams app is used, authentication relies on Microsoft single sign-on for Microsoft Teams apps.
### Provisioning
The SaaS platform is designed for auto-provisioning. When a user signs in for the first time, a customer tenant and user profile are created automatically.
### Tenant segregation
Customer data is stored in a dedicated customer tenant. Each tenant has a unique set of credentials that only allows access to data within that customer tenant.
## Customer data
### Tenant-level settings
Some configuration is stored at customer tenant level, including queue configuration and calendar and mail settings.
### User data
The following user data is stored inside the customer tenant:
* personal contacts
* contact notes
* favorites
* preferences, such as layout, user-interface language, and queue subscriptions
### Technical data
The platform stores technical data needed for the solution to function.
#### Cache data
Cache data is temporary data used to optimize performance and responsiveness. Cache data is time-limited and is discarded or refreshed after a certain time.
Data can be cached on the client or on the server. Personal data cached on the client is always encrypted to prevent unauthorized access.
#### Logging data
Standard logging does not include personally identifiable information.
When customer issues are investigated, AnywhereNow might temporarily elevate the log level to obtain detailed data needed to analyze behavior. If that log data contains personally identifiable information, it is handled only by authorized persons. After the inspection is completed, the log level is returned to normal.
## Azure regions
Attendant Console for Microsoft Teams is available from three main Azure regions.
| Region | Azure location |
| ------ | -------------- |
| EMEA | Amsterdam |
| AMER | Iowa |
| APAC | Singapore |
## Administrative approval and permissions
Attendant Console for Microsoft Teams needs access to specific Microsoft 365 resources in the customer's tenant. An administrator with sufficient privileges must grant access to these resources.
After consent is granted for the tenant, the consent prompt no longer appears for that tenant, including when a new Attendant Console for Microsoft Teams user license is ordered for the same user.
### Front-end permissions
The front end requires permissions for:
* reading all users' full profiles
* reading contact photos and other contact details
* reading presence information of all users in the organization
* reading presence status for contacts
* reading user relevant people lists
* reading contact details such as telephone number
* signing in and reading user details
* maintaining access to data that has been granted
{% hint style="info" %}
The exact list of requested permissions might change over time.
{% endhint %}
### Microsoft Teams bot permissions
An administrator can grant admin consent for the Microsoft Teams bot app registration through the Admin Portal delivered with Attendant Console.
The Microsoft Teams bot requires permissions for:
* accessing media streams in a call as an app
* initiating outgoing one-to-one calls from the app
* initiating outgoing group calls from the app
* joining group calls and meetings as an app
* joining group calls and meetings as a guest
* reading directory data
* reading online meeting details
* reading and creating online meetings
* reading all users' relevant people lists
* reading all users' full profile
* signing in and reading user profile
{% hint style="info" %}
The exact list of requested permissions might change over time.
{% endhint %}
## Data retention
Data retention covers user data, customer settings, and logging data.
### Personal user data
Personal user data is maintained by the SaaS platform for as long as the user has a valid subscription.
After the subscription is terminated or disabled, user data is maintained for 90 days. This allows the user to re-enable the subscription within that period. After 90 days, the user data is deleted and can no longer be recovered.
Personal user data can also be deleted upon a formal, verified request from the user. This includes the subscription itself and can take up to 14 days to complete.
### Tenant settings
When the last user of a tenant has been deleted, the customer tenant and its configuration are deleted automatically.
### Logging data
Logging data is maintained for up to a week unless it is used during issue investigation. Investigation logging data is deleted after the issue has been closed.
## Data residency
When a new customer is enrolled, primary and backup regions are chosen. Customer data is not stored outside those regions.
For European customers, data resides in the West Europe region in Amsterdam. North Europe in Dublin is used for backups and fallback.
Customer information is stored in an isolated, secured, and encrypted database.
## Security validation
The SaaS platform was architected using the secure-by-design principle. Security has been tested and verified by an independent third party.
Internal OWASP compliance tests and penetration tests are performed at regular intervals to help ensure the security of the solution.
The SaaS platform is ISO-27001 certified and SOC-2 certified.
## Technical operating boundaries
The product-track overview owns the canonical technical operating boundaries. See [Attendant Console for Microsoft Teams technical reference](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md#technical-operating-boundaries).
### Supported PSTN architectures
See the [canonical technical reference](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md#supported-pstn-architectures).
### Microsoft Teams desktop app requirement
See the [canonical technical reference](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md#microsoft-teams-desktop-app-requirement).
### Microsoft Phone System, calling bot, and call flow
See the [canonical technical reference](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md#microsoft-phone-system-calling-bot-and-call-flow).
### Connectivity
See the [canonical technical reference](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md#connectivity).
### Search and cache
See the [canonical technical reference](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md#search-and-cache).
### Calendar and mail
See the [canonical technical reference](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md#calendar-and-mail).
## Release policy
See the [canonical technical reference](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md#release-policy).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://atlas.anywhere.now/attendant-console/compliance-and-reference/compliance-and-technical-reference.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
