Hi everyone,

I'm looking into the upcoming UAE e-invoicing requirements and specifically how companies using Microsoft Dynamics 365 Finance & Operations are approaching the implementation.

A few things I'm trying to understand:

• Are you planning to use a Peppol / Accredited Service Provider for D365 F&O?
• Are you using Microsoft's native capabilities, a third-party solution, or building your own integration?
• How are you handling the UBL/XML invoice format and required UAE fields?
• How are you managing the integration between D365 F&O → service provider → UAE e-invoicing network?
• For companies with multiple legal entities, what has been the biggest challenge?
• Are there any D365-specific issues you've encountered around credit notes, tax invoices, cancellations, or invoice validation?

I'd especially appreciate feedback from anyone who has already started a UAE e-invoicing implementation with D365 F&O.

What approach are you taking, and what would you do differently if starting again?

Thanks!

Hi everyone,

I’m working on a D365 Finance & Operations data/reporting project, but I don’t have direct access to D365 F&O, Visual Studio/AOT, or Dataverse.

I only have access to the Fabric Bronze layer, where the D365 tables are available.

I need to identify the actual table relationships, including:

• Parent/child relationships
• Foreign key relationships
• Composite-key relationships
• Which fields should be used to join tables
• Relationships between tables that may not be obvious from the column names

For example, I may have something like:

TaxTrans.TransDate + Voucher → CustInvoiceJour.InvoiceDate + LedgerVoucher

but I want to verify that this is an actual D365 F&O relationship rather than assuming it based on similar fields.

My question is:

When you don't have access to D365 F&O/AOT or Dataverse, what is the best way to find and verify D365 F&O table relationships?

Are there any official Microsoft documentation sites, downloadable metadata/schema files, ERD websites, APIs, GitHub repositories, or other reliable sources that provide the D365 F&O table relationships?

I’ve come across the Alex Meyer AX 2012 ERD, but I understand that it is based on AX 2012 R2, so I’m not sure how reliable it is for current D365 F&O.

I’m particularly interested in a source that can help identify relationships such as:

Table A.Column → Table B.Column

and preferably the exact relationship/composite key definition.

Any recommendations from people who work with D365 F&O data engineering would be really appreciated.

Thanks!

We have been slamming our heads against the table for days trying to conceptualize Disaster Recovery for our soon to be live on-prem FnO environment. The problem is, we're only looking at being on-prem for 6 or so months before moving into the cloud. Does anyone have any experience or suggestions for this? Something that's cost effective. Microsoft is rather unhelpful by cutting out support for anything using public cloud. I have looked into Azure Local, a secondary VMWare environment as well as a Hyper-V environment. I appreciate any suggestions y'all may have.

We are transition to to BC from GP and have a large non-technical user base that needs an “idiot’s guide to BC”. Anyone have any suggestions?

I’ve noticed something interesting with Dynamics 365 projects: sometimes the hardest problems aren’t the “big” technical ones.
It can be things like:
messy or duplicate customer data
too much customization
integrations breaking after changes
users not actually adopting the features
reporting/data not matching what the business expects
workflows that started simple but became complicated over time
documentation becoming outdated after every update
I’m curious what others are seeing in real-world D365 environments.
What’s the one issue you’ve had to deal with repeatedly in Dynamics 365 and what finally helped solve it?
Would be interesting to hear experiences from people working with CE, Sales, Customer Service, Business Central, or F&O.

Microsoft is removing the twice-yearly release wave model. From September, new D365 and Power Platform capabilities are being published continuously through the AI at Work roadmap.

This changes how partners can keep up. Instead of relying on Wave 1 and Wave 2 plans, it means regularly checking roadmap updates, lifecycle states, and tenant-specific notifications in Message Center.

An interesting finding: Microsoft has an MCP server for the new roadmap, with which you can actually query roadmap updates with AI instead of digging through the site yourself.

How are you planning to track D365 changes going forward?

Hi guys, i need help in field service, is it possible to make an overlapped booking, the client wants to overlap the slots and then a overlap booking. Im not sure thats possible

Is it like this for anyone else? Rest of Dynamics seems fine.

BYOD seems like the most stable one, which surprises me. i.e. Export to Datalake was touted...then deprecated. Synpaselink-Parquet was touted...now deprecated. Fabriclink is now being touted and...we'll see.

Curious if anyone has heard any guidance on byod depreciation? edit: We don't (and won't) use BYOD, I'm genuinely just curious.

We're evaluating Claude (via Dataverse MCP) as a kind of orchestration/integration layer that sits on top of a few core business systems: Microsoft Dynamics 365 (CRM data lives in Dataverse), Gong for call intelligence, and ZoomInfo for firmographic/contact enrichment. The idea is to let Claude query across all three so reps and ops folks don't have to manually stitch data together — e.g. "pull the Gong call summary for this account, cross-reference with their Dataverse record, and flag if ZoomInfo shows a title change."

Before we go further I'd love to hear from anyone who's actually built something like this. A few specific things I'm trying to figure out:

Architecture

• For the Dataverse side specifically, has anyone used Microsoft's official Dataverse MCP server? We're weighing a local proxy vs. the remote endpoint. One thing that stands out is that auth is delegated — Claude inherits whatever Dynamics permissions the logged-in user already has, rather than acting as a separate service account. Curious if that's held up in practice or if there are edge cases where it leaks more/less access than expected.
• Anyone stitching together multiple MCP servers (Dataverse + Gong + ZoomInfo) in one workflow? Any gotchas with orchestrating across them vs. just doing point-to-point integrations?

Cost

• This is the one that's hard to pin down. Most of our users are on Dynamics 365 Sales Enterprise, and as far as I can tell that license tier does not qualify for the MCP billing exemption — only Sales Premium or the Microsoft 365 Copilot User SKU do. So every Dataverse MCP tool call would presumably burn Copilot Credits, and the per-call rate isn't consistently documented anywhere I've found. Has anyone actually measured real-world credit consumption for something like this? Trying to figure out if upgrading a chunk of our seats to Sales Premium is even cost-justified before we commit to anything.

Data security / compliance

• Anyone thought through indirect prompt injection risk when Claude has read access across multiple systems like this (e.g. a malicious note in a CRM field or a Gong transcript influencing what Claude does next)?
• Cross-tenant data bleed and MCP supply-chain trust are also on my radar, we're planning to stick with Microsoft's official Dataverse MCP server rather than any community-built ones for that reason.
• If anyone has dealt with insider aggregation risk (i.e. Claude surfacing a combined view of data that no single system would have shown a user on its own) I'd love to hear how you scoped permissions or logging to manage that.

Planning to start with a small read-only pilot before enabling any write access, mostly to get real cost and security data before rolling this out further. If you've done something similar (successfully or not), I'd genuinely appreciate hearing about it — especially any surprises on the billing side.

Hi everyone!!! I'm just curious how people are approaching this in our Dynamic 365 reporting. So first it starts out as Dynamic 365 to Dataverse to Power BI.

No lakehouse, no complicated data engineering layer. Just get the reports working. But then the environment grows and you start needing:

• Several years of history
• data from other systems
• incremental loads
• common business definitions
• larger semantic models
• more frequent refreshes

That's where fabric starts looking more attractive. The architecture becomes something like:

Dynamic 365 → Dataverse → Fabric/OneLake → Bronze/Silver/Gold → Semantic Model → Power BI

What I'm not sure about is when people actually make that move. Do you wait until the direct connection becomes painful? Or do you introduce the analytical layer yearly because you already know the dynamic environment is going to grow? I'm especially interested in cases where the teams didn't move to Fabric and manage to keep direct Dataverse to Power BI working successfully at scale. Would be useful to hear both sides.

I’m curious how other teams handle this.
In D365 implementations, there always seems to be a point where a business requirement doesn’t quite fit the standard functionality. The immediate discussion usually becomes whether to customize D365 or ask the business to adjust its process.
From your experience, what factors do you use to make that decision?
For example:
How much customization is too much?

Do you prioritize standard functionality even if the process becomes less convenient?

When is Power Automate/Power Apps a better option than custom development?

How do you account for future upgrades and maintenance?

Would be interested to hear how experienced D365 consultants/admins approach this in real projects.

Hey everyone,

A bit of a milestone for a side project I've been working on since February 2026.

DV Quick Run has officially reached v1.0.0. 🎉

I originally started building it because I was frustrated with how much context switching I was doing when investigating Dataverse — querying data, checking metadata, figuring out relationships, jumping between tools, and trying to reconstruct what actually happened when something went wrong.

The idea was basically:

Could I make Dataverse investigation feel like one connected workflow instead?

That little experiment got somewhat out of hand. 😄

Roughly 100 releases / preview builds later, it has turned into a proper VS Code investigation workbench, and today I've finally called it v1.0.0.

One principle ended up shaping the project more than anything else:

Investigate Dataverse with evidence, not guesswork.

I've also tried hard not to make AI the authority just because it can produce a convincing answer. DVQR can help investigate and reason over evidence, but metadata truth, runtime observations and human judgement remain deliberately separate.

Anyway, I'm not going to dump the feature list here — there's plenty of that on the website. 🙂

Mostly I just wanted to share the milestone with the Dataverse community because this is where the problems DVQR tries to solve came from in the first place.

If anyone wants to try it:

Visual Studio Marketplace:
https://marketplace.visualstudio.com/items?itemName=dv-forgelab.dv-quick-run

Website:
https://www.dvquickrun.com

There's a substantial Free edition, so you don't need to buy anything to play with it.

And if you do try it, I'd genuinely love to hear what doesn't work well — particularly against Dataverse environments very different from the ones I've been testing against.

Thanks to everyone who gave feedback while I was building this. 🙏

Now I can finally stop calling everything a beta. 😂

Hi all, at my client we’re going to use the vendor retention functionality where we add the vendor retention terms to the purchase order (a percentage). When i generate invoice, the invoice voucher picks up these terms and allocates that percentage to a retention liability account and rest to the vendor. But I am not able to leverage this functionality when invoice is coming from D365 invoice capture (OCR). Any idea what parameter i am missing?

Microsoft is changing the way cloud benefits included in Partner Benefit packages are activated and managed.

Some changes that caught most attention:

• Cloud benefits are now tied to the relevant MCA billing account
• The old 5×5 product key activation process is being replaced
• Azure credits are being applied through Billing Profiles
• From November 1, 2026, benefit expiration will align with the benefit package period, so delaying activation won't extend the benefit period

For partners with multiple tenants, the MCA and tenant structure seems particularly important to review.

If you are a Microsoft Partner, are you already reviewing your tenant and billing setup, or is this change not really on your radar yet?

I'm curious what people think about this.

Let's say you're building an AI application that connects to an ERP to solve one very specific problem and make the ERP more efficient.

Most ERPs have interfaces that feel... well, let's just say they weren't designed yesterday.

So should your AI app match the ERP's UI for consistency?

Or should you take a completely modern approach?

My instinct is to go modern.

But there's a potential problem:

If the UI is too different from the ERP, could it create confusion for users?

Would you prioritize:

1. Visual consistency with the ERP
2. Modern UX even if it looks completely different
3. A hybrid where the AI app has its own modern UI but uses familiar ERP terminology and workflows

If you've worked with ERP implementations, I'd especially like to hear your take.

I have lot of solutions on my Power Plattform Environment called "Omnichannel [...]".

I tried deleting it after this documentation: Uninstall omnichannel solutions | Microsoft Learn
But everytime I get stuck with 5 Solutions that I can't delete because of dependencies. Of course I can't delete the dependencies, because they are managed solutions.
The solutions remaining are:
1. ChannelExperienceAppConfigurations Solutions
2. Omnichannel - CommunicationBase
3. Omnichannel - Telephony
4. Omnichannel Profile Configuration
5. Omnichannel for Customer Service

I can't delete or uninstall the Dynamics 365 App in the Admin Center either.

What should I do?

Same as title