Hi Naza
Not sure if this answers your question... What I say here is also open to correction - anyone is welcome to correct me.
When you want to use embedded PowerB in D365 workspaces, the report runs directly in d365 for operations. When it runs directly in D365 for operations, it interacts directly with the database called AxDW (via directQuery), which is the data warehouse. To create tables and views in the data warehouse, you need to deploy entities in the entity store. This means that whenever someone does something on the embedded power BI report, like drill down or filter or something like that, the embedded report sends a query directly to the DB and brings it back, which means that the data on the embedded report is always real time (It's as old as the data in AxDW. To refresh the data in AxDW, the entity stores need to be refreshed).
When running a report deployed to PowerBI.com, the report stores data in it's own database independent of D365O. When someone interacts with a report likes this, it is always interacting with data on it's own database, or it's own data warehouse based on D365O's entities. When someone changes data in D365O, the report won't see the change until it's data is refreshed. The only way to refresh the data on a report like this is via OData.
Therefore, reports deployed to PowerBI.com don't touch AxDW. They're constructed form the entity store and then run off their own Datawarehouse.
Embedded reports use AxDW which is constructed form the entity store and refreshed from the entity store.
