Dynamics 365 Customer Insights - Data

-We have customers that wants Power pages be made available in South Africa Region, some of our customer their data is sitting outside South Africa, since the availability of data centers in South Africa including the Business Applications, now they would love to move/migrate to South Africa Region, now the challenge of moving of our to our region will be impacted with the fact that power pages are not available in their region.



In an event Microsoft is busy with power pages in South Africa can we have timelines to advise our customers.

Show straightforward error information in the CI–Data UI for each step (ingestion, unification, enrichment, export). Include what failed, where it failed, a reference ID, and plain‑language guidance to fix it. Let users copy/export the details, open the related run history, and choose how much detail they see based on their role. Use the existing diagnostic events for consistency, reduce support tickets, and enable self‑service troubleshooting.

When creating/editing Microsoft Dataverse datasource, on the Configure page, there is no search field available and users have to scroll up and down to identify the tables to select.

A more complete and complex data model turns this task harder when there are hundreds or thousands of entities from the list.

A search field would improve this experience, requiring less time to identify the table to add and avoid potential error prone scenarios when table names are very similar.

Seamless experience with search field ("Search tables") can be seen in Data > Tables, in order to select the required table.

Based on the document Exclude bot interactions - Dynamics 365 Customer Insights from Microsoft, inflated open rates are a known occurrence due to the fact that bot protection does not apply to email opens. As a result, nonhuman traffic can artificially increase open rates, leading to misleading analytics.

I would like assistance in identifying a solution to prevent this issue from occurring in the future

Sending alerts to notify administrators when there is any restarts, DB availability movements or container move to ensure transparency and customer visibility regarding these issues.

Purpose of Notifications

The goal is to proactively inform administrators about infrastructure-level changes that could impact system performance, data availability, or customer experience. These alerts would serve two key purposes:

1. Transparency: Ensuring that internal teams are aware of backend operations that may affect service continuity or performance.
2. Customer Visibility: Allowing support teams to communicate confidently with customers about any disruptions or changes, backed by real-time system insights.

What Each Alert Covers:

• Restarts: Alerts when services or containers are restarted—whether planned (e.g., updates) or unplanned (e.g., crash recovery).
• DB Availability Movements: Notifications when databases are moved between nodes or regions, which may affect latency or access.
• Container Moves: Updates when containers are relocated for load balancing, scaling, or maintenance purposes.

Implementation Suggestions:

• Integrate with existing monitoring tools (e.g., Azure Monitor, Application Insights).
• Use email or dashboard alerts for delivery.
• Include metadata like timestamp, affected resources and expected impact.

In our case, we want to add an event registration form to our website, which means that people who are not yet in our contact database could register. They would fill out an event registration form, not a marketing form and therefore would not have consent for marketing communication. Without this prior consent, they would be unable to receive any emails, such as the event confirmation email.

Unfortunately, this approach doesn’t meet our current requirements. We need a solution that accommodates non-registered contacts in the system who still need to receive event-related emails.

While I have no issue using a marketing form (since it would include the DOI process), it does not have the event-specific fields, such as session summaries or speaker information. Additionally, I would not be able to integrate the marketing form into the event system, where registrations, check-ins, and other event-related actions are managed.

As it stands, according to the current logic, a new contact must register twice: first with the marketing form, then with the registration form and finally confirm the DOI email.

However, this issue could be resolved if the registration form had the same functionality as a marketing form, triggering the DOI process and sending the automated first DOI confirmation email.

We would appreciate any suggestions on how this process can be streamlined while still meeting the necessary requirements.

we face issues with the functionality of publish options for forms.

We would like to use the variant "Embed Form". Currently the generated JavaScript code does not consider any CSS classes and styles in Real time markeitng email.

So we expect the Java Script generator to provide more details such as header, fonts, footer details so that it will reduce the manual option to entering the code for rest of the features and options always.

The tables ending in "-analytics" are generated by one or more Insights applications as Customer Service, or Field Service... This tables consumes Dataverse storage and sometimes to remove them is needed following a complex process removing Microsoft solutions from the instance.

As idea i think that should be better have a central dashboard to can turn of or on the features, and if the features are off it remove the -analytics tables.

Create an Out of the box entity ( to store all the activities performed within CI like user addition, refresh success/failures, user activities etc ) in Customer Insights ( B2C and B2B ) instances soon after ingesting first data source. which will hep us to build a report based on the system entity to track CI system activities.

Create Power Query connectors for the standard Social Media platforms so that clients don't have to build them custom or purchase third party tools. These are very common and should be available out of the box:

• Facebook/Facebook Ads
• Instagram/Instagram Ads
• TikTok/TikTok Ads
• Twitter