BYOD purpose in D365F&O

(3) Share

Report

Posted on by CU22111441-0

Hello, I have searched in Google and found many blogs about BYOD. I understood the BYOD configuration required.

But still I have one confusion, when the BYOD is recommended to use. I mean the actual needed to implement BYOD in D365F&O. What is the purpose to use of this.

Please provide me the thoughts. thanks

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (6)

Answers (4)

Verified answer

Aymen CHELBI 586 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hello,

BYOD allows you to export data entities from D365FO into your own SQL Server database, instead of using the Entity Store (AXDW) or Data Entity, which isn’t accessible to end users in production. With BYOD, you can export data manually, through batch jobs, via the standard DMF export projects.

To use BYOD, you first configure your SQL database in the Data management workspace under Configure Entity export to database. After that, you can publish entities to create the corresponding SQL tables, and then run DMF export jobs targeting your BYOD database.

Advantages

Full access to exported data in your own SQL database

Ability to filter data during export

Can be automated through batch jobs

Disadvantages

One-way integration (export only)

For more detail : Bring your own database (BYOD) - Finance & Operations | Dynamics 365 | Microsoft Learn

Best regards,

Was this reply helpful? Yes No
CU22111441-0 on at

Like (0)

Report
Copy link

Link copied!

Thanks Aymen, I understood well the steps you mentioned. Finally, you mentioned that export the data in to BYOD database.

Now, my questions is , When we completed the export process of BYOD, then next where we used that BYOD db in real world.

Is it strongly recommended for Power BI?

Please give me your thoughts.

Was this reply helpful? Yes No
Verified answer

Sohaib Cheema 49,677 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi ,

BYOD was introduced mainly to address reporting needs. When Microsoft blocked access to the production database with the release of AX7, people still wanted to create reports using direct SQL. Microsoft introduced BYOD so you can export Dynamics data to your own Azure SQL database and work with it as needed. Most commonly, it’s used to build Power BI reports.

I have also seen people use the BYOD database for integration purposes, sometimes.

Once you have data in your own Azure SQL instance, do whatever you like with it. There are no restrictions, it is your data in your own Azure SQL instance.

Was this reply helpful? Yes No
Verified answer

Martin Dráb 239,040 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

There may be many reasons why you want to export to your own database. It may be for reporting, analytics, integration or so. It also you to use existing tools that connects to databases (you don't have access to the F&O production DB), you can combine data from multiple systems, transform the data to meet particular needs and so on.

Nevertheless note that BYOD is considered a legacy solution. Check out Transition from legacy data integration services, for instance, to learn about the current options.

Was this reply helpful? Yes No
CU22111441-0 on at

Like (0)

Report
Copy link

Link copied!

Thanks Sohaib, as you said "I have also seen people use the BYOD database for integration purposes."

So, except Power BI report, what are other integration is possible with BYOD?

Please give me the thoughts. thanks!

Was this reply helpful? Yes No
Verified answer

Sohaib Cheema 49,677 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

When you do not want to provide direct access to your system (D365 FO) and an external party requires read-only access to one or more entities, you can grant such integrations read-only, uni-directional access via BYOD.

You also need to be mindful of the timing in these integrations. For example, if you need real-time data, BYOD will not work, as it is not real-time.

You can also use it in integrations where you need to compare two datasets to determine the difference. For example, what is the list of vendors in D365 FO in the BYOD (as data in the BYOD came from D365 FO), and compare this list with another list coming from a third-party system to identify the new records that need creation (although for the creation process, you can use other ways such as recurring integrations, etc.).

Was this reply helpful? Yes No