> 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/operate/reporting-operations/reporting/dialogue-insights-reporting-environment.md). # Dialogue Insights reporting environment Review Dialogue Insights historic reporting refresh timing, Fabric workspace time zones, and storage dependencies that affect report downloads. Use this page to review operational details that affect Dialogue Insights historic reports. The page is intended for administrators who monitor reporting freshness, understand the assigned UCC Service region, and support stored recording, voicemail, and transcript files that may appear in Dialogue Details. ## Data residency and Fabric resources Dialogue Insights uses Microsoft Fabric for customer-specific real-time and historic dialogue data. The Microsoft Fabric resources used by Dialogue Insights are hosted in the AnywhereNow-managed Azure tenant. Data separation is implemented with customer-specific Microsoft Fabric resources. The resource set includes customer-specific Eventstreams, Eventhouse databases, semantic models, and report workspaces. Audio recordings, voicemail recordings, and UCC behavior management data are not stored in Microsoft Fabric. ## Customer access to reports and data models Workspace content is readable only by members of the Microsoft Entra ID security group for the customer. Authentication for this access is handled through Microsoft Entra B2B collaboration. Users already present in the Microsoft Entra B2B collaboration tenant are automatically assigned to the customer-specific security group based on their domain and tenant ID. Users not yet known in that tenant can be added through OnePortal. Access to OnePortal is separate from report access. Users can open a report through its customer-specific URL without OnePortal access, but must still belong to the customer's security group. For the report URL procedure, see [Open Dialogue Insights](/use/monitor-and-report/dialogue-insights.md#open-dialogue-insights). ## Historic reporting refresh Dialogue Insights historic reports and their datasets are documented to refresh daily at **00:30** in the time zone of the Fabric workspace used by the reporting environment. {% hint style="info" %} If a historic report is already open while the underlying dataset refreshes, refresh the report manually in the browser or app before relying on it for the refreshed dataset. {% endhint %} Use the assigned Fabric workspace region to interpret the **00:30** refresh time. | Fabric workspace region | Time zone | | ----------------------- | ------------------------------- | | `EMEA-GWC` | `W. Europe Standard Time` | | `APAC-SEA` | `Singapore Standard Time` | | `NORA-CUS` | `Central America Standard Time` | ## UCC Service region mapping The UCC Service region determines which Fabric workspace region is used for the reporting environment. | UCC Service region | Fabric workspace region | | --------------------------------- | --------------------------------- | | `EMEA-WEU (West Europe)` | `EMEA-GWC - Germany West Central` | | `EMEA-GWC (Germany West Central)` | `EMEA-GWC - Germany West Central` | | `EMEA-SZN (Switzerland North)` | `EMEA-GWC - Germany West Central` | | `NORA-CUS (Central US)` | `NORA-CUS - Central US` | | `APAC-SEA (South East Asia)` | `APAC-SEA - South East Asia` | | `APAC-AUE (Australia East)` | `APAC-SEA - South East Asia` | ## WebAgent history From DC2025.02a, Dialogue Cloud Neo customers use Dialogue Insights for WebAgent history. Dialogue Insights starts gathering data after the DC2025.02a bundle update, so history becomes available from that point onward. New customers onboarding to Dialogue Cloud Neo (Connect) or Dialogue Cloud Neo (Unify) use Dialogue Insights only for WebAgent history. Existing customers upgrading to Dialogue Cloud Neo can continue using an existing customer-owned CDR database together with Dialogue Insights where that configuration is already approved. ## Reporting impact of stored files Dialogue Details can show download links for stored files associated with an audio dialogue. Link availability depends on whether the relevant file has been saved and is available for the dialogue. | File type | Reporting impact | Operations reference | | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | Recording | A recording link can appear in Dialogue Details when the recording file is saved and available. | [Manage call recordings](/operate/recording-and-interaction-data/manage-call-recordings.md) | | Voicemail | A voicemail link can appear in Dialogue Details when the voicemail file is saved and available. | [Manage voicemails](/operate/recording-and-interaction-data/manage-voicemails.md) | | Transcript | A transcript link can appear in Dialogue Details when transcript recording to SharePoint is enabled and the transcript file is available. | [Manage transcripts](/operate/recording-and-interaction-data/manage-transcripts.md) | ## Operational checks When investigating reporting freshness or missing download links: * Confirm the UCC Service region and corresponding Fabric workspace region. * Interpret the daily **00:30** refresh in the Fabric workspace time zone. * Refresh already open reports after the dataset refresh window. * Check the relevant recording, voicemail, or transcript storage path before treating a missing Dialogue Details download link as a reporting issue. --- # 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/operate/reporting-operations/reporting/dialogue-insights-reporting-environment.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.