One Admin

Power Platform Admin

Center (PPAC)
Integration with LCS

Lane Swenka
Andreea Bunduc
Corina Balan
Saurabh Kuchhal

1
Dynamics 365 Product
guidance
Implementation Guide General Case
guidance studies
Collective experience gained through
thousands of Dynamics 365 implementations

References to Guide Checklists

other guidance Experience

Highlights Recommended
deliverables
Conceptual
graphic
support

Available at: https://aka.ms/d365implementationguide

Microsoft Dynamics 365 implementation guide | Microsoft Learn
2
Agenda
Challenges
Vision & Roadmap
Power Platform Integration
Demo
Implementation Scenarios
Q&A

3
Challenges |
Bridging the gap for admins

4
Not just a single gap…
• F&O admins are increasingly needing to connect to Dataverse and Power
Platform, but this was not managed by LCS where F&O admins live and breathe

• Power Platform admins didn’t recognize the new F&O-connected environments,

and started to delete them in their admin portal

 Getting integration setup manually is very technical and error prone

 8 page document plus constantly changing requirements

 Multiple integration technologies to choose from (Virtual tables, Business

events, Dual-write, Data Events, Logic apps etc.) and all used manual and
separate connections

5
One Admin – Vision & Roadmap

6
The convergence stack

Plugins

X++ forms
Relational embedding in UCI
databases

Visual Studio

Files and
blobs Log files

Authentication

Business events
One Admin Center
Semi-structured
(LCS + PPAC)
data
Dual write Authorization

Mobile ELM, ALM

Offline
Search and
Common Data
Virtual entities Auditing Find data
Model Data lake 7
 One Admin -
F&O as an app,
not an environment

8
 Roadmap – Capabilities by milestone

LINK
TRY
OPERATE
MIGRATE

LINK TRY OPERATE MIGRATE

Customers can link F&O Customers can deploy Customers can deploy Customers can migrate
apps with a Power Platform unified Trial Developer, Sandbox, and their LCS project and
environment with Dataverse environments with Production environments environment We Are Here
via Dataverse and F&O all via with Dataverse and F&O management over to
Power Platform Integration. PPAC. all via PPAC. PPAC.
No new LCS
F&O customers

Microsoft Confidential: Content is shared under NDA with Microsoft CAB members 9
Power Platform Integration

10
Features that are enabled via Power Platform Integration

Dual-write

Virtual tables

Business events

Add-ins
• Export to Data Lake
• Finance Insights
• Inventory visibility service
• Etc.

Customer-managed key (CMK) / Lockbox encryptions

Embedding PowerApps in F&O UX

More and more…

11
 Power Platform linking concepts
Power Platform Integration (PPI) Linked Dual-write (DW) Linked
• Integrate finance and operations apps data with the Dataverse • PPI linking will shortly become a prerequisite for dual-write
platform by using virtual tables, business events, and dual-write linking
features. • Link/Un-link will be replaced by a new feature “Reset”
• Install add-ins and connect them with your finance and
operations apps
• Link to a new Dataverse or to an existing Dataverse instance

12
Dual Write : Link/Unlink becomes Reset
• Prevent linking F&O to a different Dataverse than used by Power Platform Integration
• Single connection string between F&O and Dataverse for VE/BE/DW/Add-ins
• Simplified reset capability will clear configuration tables after Database Refresh/Environment
copy
• Reset button will be available starting Feb 2023 (unless you reach out to support team)
• In case of mis-match, please fix connection with Power Platform Integration by Jan 2023
• Raise support ticket if you need help (mention “ICM349669515”)
• After Jan 2023, need to delete and re-deploy the environment

13
 Environment Lifecycle Operations (ELOs) Concepts – LCS & PPAC

Lifecycle Operation LCS Terminology PPAC Terminology Supported in LCS Supported in

API? Power Platform
API / Tools?
Create Deploy Provision No Yes

Copy Database Refresh Copy Yes Yes

Backup Database Export Backup (Custom & Yes Yes

System-defined)
Restore Point-in-time restore Restore (Custom & No Yes
System-defined)
Reset N/A Reset No Yes

Convert to Production N/A Convert to Production No Yes

Delete Deallocate / Delete Delete No Yes

Microsoft Confidential: Content is shared under NDA with Microsoft CAB members 14
 Enable Power Platform
Integration when F&O
apps environment is
being deployed – to be
removed soon*
• If we choose Yes to configuring the Power
Platform integration, a new Dataverse
environment with database is provisioned
with solutions as per selected template. 3
templates are available:
• Dynamics 365 Standard
• Dynamics 365 Standard with dual-write
• Project Operations

• If we choose No to configuring the Power

Platform Integration, a Dataverse
environment is still provisioned without
database. The database for this environment
cannot be added from the Power Platform
Admin Center.

* For sandbox and prod, not CHE 15

Enable Power Platform
Integration after F&O
apps environment is
deployed
• In the future, the only way to enable Power
Platform Integration will be via Setup button
in LCS. Button will be visible if we choose No
to enabling Power Platform Integration at
F&O apps environment creation.

• With Setup button press, if we choose No to

using a different environment, the
automatically provisioned Dataverse
environment will get its Database enabled,
and solutions will be installed as per selected
template.

• With Setup button press, if we choose Yes we

can link F&O apps environment with an
existing Dataverse instance. The Dataverse
environment created automatically can be
safely deleted after setup with existing
environment completes.

16
Demo –
Setup Power Platform Integration
One Admin – Demo

18
Implementation scenarios

19
SCENARIO: Customer wants to create a new f&o apps environment, and will not use features such as Export to
Data Lake, integration with Dataverse via Dual-Write, Virtual Tables.

Action: While creating a new f&o apps environment, do not select Configure Power Platform environment.

PP environment is still created with linking in place, but cannot use Dataverse capabilities and features such as Export
to Data Lake Add-In, dual-write, virtual tables.

Tip: You can always enable the Dataverse capabilities as a post-deployment action (for
Microsoft managed environments).
20
SCENARIO: Customer wants to create a new f&o apps environment, and use any of the available Add-ins,
integration with Dataverse, or Project Operations. Let's call it as “linked” environment.

Action: Patterns:
a) While creating a new finance and operations apps (f&o apps) • Use the post-deployment
environment, do not use Configure Power Platform environment. After option a) as the default one,
deployment, use the Lifecycle Services (LCS) Setup button as it is valid for both new PP
environments, as well as
existing ones.

Anti-patterns:
• Use option b) if there is
b) While creating a new f&o apps environment, use Configure Power already a PP environment to
Platform environment link with the new f&o apps
environment.
and
Select the appropriate template per your
requirements.

Tip: Think of f&o apps and Power Platform (PP) as one environment. Maintain 1:1
mapping between f&o apps and PP environment.

21
SCENARIO: Customer wants to create a new f&o apps environment, but to link it to an existing Power Platform
environment.*

Action: Anti-patterns:
• Enable the Power Platform
While creating a new f&o apps environment, integration during the
do not use Configure Power Platform deployment of the f&o apps
environment. environment.

After deployment, use the LCS Setup button ->

Use a different Power Platform Environment
and specify the ID of the existing
PP environment.

Note: Additional solutions will be installed in Dataverse.

*Not available for CHEs

Tip: Tip: Do not forget to delete the Power Platform environment which was used by the
LCS – PPAC link. It is not deleted automatically.

22
SCENARIO: Dual-write initial setup from LCS
Customer created linked environment with the “dual-write template”. Next the dual-write setup needs to be triggered.
In this slide, let’s see linking from “LCS”.

Action: Go to LCS -> Power Platform integration section and select Link to Power Platform environment.

This will enable all* Legal Entities for sync between f&o apps and Dataverse.

Make sure to install any other necessary solutions from AppSource,

as only dual-write core is installed with the Dynamics 365 with Dual-write
(as shown in snapshot on the right)

Apply solution(s) in the dual-write workspace. *Initial/Live sync LE limits still apply

Tip: In case of live sync more than 250 LEs, reach out to support team.
Linking via LCS is the recommendation!
23
SCENARIO: Dual-write initial setup from f&o apps
Customer created linked environment with the “dual-write template”. Next the dual-write setup needs to be triggered.
In this slide, let’s see linking from f&o apps (Data management workspace).

Action: Choose the same environment as defined in the LCS -> Power Anti-Patterns:
Platform integration section.
• Selecting a different PP
environment than the one
defined in LCS.

Select legal entitles for sync via dual-write.

Review the Health check and the Summary -> Submit.
Make sure to install any other necessary solutions from AppSource, as only
dual-write core is installed.
Apply Solution.

Tip: This option will be removed soon.

24
SCENARIO: Delete linked f&o apps environment

Action: Anti-Patterns:
• Delete f&o apps environment from LCS
• Only deleting the f&o
apps environment
from LCS.

• PPAC link is removed, but Power Platform environment is not deleted.

• Delete the Power Platform from PPAC.

Tip: If looking to re-deploy the f&o apps environment with same name, unlink from
dual-write workspace first.

25
SCENARIO: Delete linked Power Platform/Dataverse environment.

Action: This is not possible, the f&o apps environment needs to be deleted Anti-Patterns:
first.
• Only deleting the f&o
Note: PPAC -> environment -> Delete will result in an error.
apps environment
from LCS

Tip: Delete the f&o apps environment from LCS first.

26
SCENARIO: Customer realized that one of the f&o apps sandbox environments is linked with a different Power
Platform environment in LCS than the one used for dual-write.

Action: If the Setup button is enabled, leverage it and specify a different PP Anti-Patterns:
environment.
• Ignore the LCS warning.
Otherwise, consider that the link is irreversible; the f&o apps environment
needs to be redeployed (deleted and recreated).
When the f&o apps environment is redeployed, do not enable the Power
Platform integration at creation.
Leverage the Setup button to specify the Power Platform environment used
for dual-write.
Note: LCS will show the status as below

Tip: If the Power Platform integration has been leveraged already (e.g. for Data Events),
manual reconfiguration might be required to bring them into the dual-write
environment.
27
SCENARIO: After being live for a while, customer realized that the f&o apps production environment is linked with
a different Power Platform environment than dual-write and needs to be corrected.

Action: Anti-Patterns:
If the Power Platform integration is not setup (Setup button is available), • Not checking the linking
proceed with the self-service setup and use an already existing Power between f&o apps and PP
Platform environment. environment.

If the Power Platform integration is setup, reach out to the Support team with • Keep using with wrong/non-
all details such as: production PP environment.
• What is the ask
• What are the environment details
• Why is the ask

Tip: It is critical to ensure that the mismatch is resolved as soon as possible. Please be
aware that the support path is available for a limited period and it is valid for existing
customers only, new customers should follow the best practices.
28
SCENARIO: Customer realized that the f&o apps environment is linked with the correct Power Platform
environment in LCS, but dual-write linking is wrong.

Action: Go to f&o apps -> Data Management workspace -> Dual-write -> Anti-Patterns:
Unlink environment.
Delete the data from key tables: • Keep using with wrong
• DualWriteProjectConfiguration Dataverse environment.
• DualWriteProjectFieldConfiguration
• BusinessEventsDefinition

In the same workspace, leverage New link to environment and choose the
Power Platform environment used in the LCS – PPAC linking.

Note: In the near future, use Reset button.

Tip: Once the dual-write PP environment is changed, additional steps will be necessary to
ensure data alignment (initial sync or data migration).

29
SCENARIO: Customer wants to link an existing PP environment which is linked to another f&o apps environment.
This might happen when converting PP linked sandbox to production.

Action: Since the link is irreversible and cannot be changed from either
PPAC or LCS, the f&o apps environment already linked needs to be deleted.

Once the f&o apps environment is deleted, the link will disappear from PPAC
and the existing PP environment can be linked to another f&o apps
environment.

Note: attempting to link the existing PP environment without unlinking will result in an error:

Tip: If during cutover, you do not want to delete the previously linked f&o apps
environment, consider creating a new PP environment, instead of converting the existing
linked sandbox to production.
Further activities might need to be performed to ensure that the linking is finalized.
Consider also the impact on data that needs to be synched via dual-write.
30
SCENARIO: Customer is already live with Dynamics 365 Finance and plans to go live with Dynamics 365 Sales, with
dual-write in scope. For the Finance implementation, Add-Ins, Data events have been leveraged.

Action: Anti-Patterns:

Since Power Platform integration capabilities have been • Not leveraging the
leveraged, there is already a PP environment used by the LCS existing PP
– PPAC link. environment while
planning to integrate
Pay attention to use that environment instead of creating a the Dynamics 365
new one in PPAC, as you will not be able to use the new apps.
environment.

The necessary dual-write solutions need to be installed.

Tip: The LCS – PPAC link is irreversible.

31
SCENARIO: Customer is already live with Dynamics 365 Sales and plans to go live with Dynamics 365 Finance. There
is no plan to integrate the Dynamics 365 apps via dual-write, but Data events are in scope.

Action: Anti-Patterns:

Two possibilities: • Not leveraging the

existing PP
• Leverage the existing PP environment, without installing the dual-write
environment while
solutions. This is the preffered option, as it leaves the possibility for
integration between the Dynamics 365 apps as a future step. planning to integrate
the Dynamics 365 apps
in the (near) future.
• Do not use the existing PP enviornment, but the one created automatically
when the f&o apps environment was deployed. This option will lead to
two PP production environments running and will remove the possibility
for an out of the box integration between the Dynamics 365 apps.

Tip: Think about the linked PP and f&o apps environments as one environment with
multiple apps.

32
SCENARIO: Customer wants to refresh the f&o apps database and copy the Power Platform environment, when
both source and target environments are linked:

Action: Use Refresh database to do a database copy of f&o apps; Use Copy Patterns:
in PPAC to do the PP environment copy. • Environment actions
such as copy or restore
After the two operations are completed:
• In Dataverse, the entire codebase will be replaced – the solutions that should be done in
were removed need to be re-installed. Consider dependencies carefully. paralel for both Power
• Dual-write workspace (the experience will be updated soon with a Reset Platform and f&o apps
option)
- Stop all table maps
- Unlink (the link will come from the source) Anti-patterns:
- Delete the data from tables: DualWriteProjectConfiguration, • Copying only the PP
DualWriteProjectFieldConfiguration, BusinessEventsDefinition environment
- Relink with the correct environments
- Start the maps without initial synch

Tip: The PPAC-LCS link is not affected by environment copy, that will be preserved.

33
SCENARIO: Customer wants to refresh the f&o apps database and copy the Power Platform/Dataverse
environment, when both source and target environments are linked – continuation:

Action: Patterns:
• Virtual entities: • Environment actions
• If they were not present in the source environment, they need to be
enabled
such as copy or restore
• If they were present, but a schema changed occurred, they need to should be done in
be refreshed paralel for both Power
• Business events: Platform and f&o apps
• Consider rebuilding the Business events catalog
• Active business events are not copied, they need to be recreated
• Data events: Anti-patterns:
• Ensure that the Virtual entities are present in Dataverse • Copying only the PP
• Active data events need to be recreated environment

Tip: If you decide to copy only PP (not recommended), the same steps apply;
additionally, a dual-write initial synch or data migration might be necessary.

34
SCENARIO: Customer wants to restore the database from an unlinked f&o apps environment to a linked f&o apps
environment. For example, bringing unlinked Gold environment to linked Test environment.

Action:
• The dual-write, Business events, Virtual entities steps highlighted in the previous scenario need to be applied

• Additionally, steps such as initial synch or data migration are necessary to align back the environment.

Tip: Try to work in pairs of environments (f&o apps and PP) and avoid copying from
unlinked PP or unlinked f&o apps environments.

35
SCENARIO: Customer wants to copy an unlinked Power Platform environment to a linked Power Platform
environment. For example, copying an unlinked Data migration environment to a linked Test environment.

Action:

• After copy, the solutions that enable the Power Platform integration need to be re-installed (according to the
template)

• The dual-write, Business events, Virtual entities steps highlighted in the paired scenario need to be applied

• Additionally, steps such as initial synch or data migration are necessary to align back the environment.

Tip: Try to work in pairs of environments (f&o apps and PP) and avoid copying from
unlinked Power Platform or unlinked f&o apps environments.

36
SCENARIO: Customer wants to restore the database from a linked f&o apps environment to an unlinked f&o apps
environment. For example, to a troubleshooting environment which is not linked.

Action:
• Since the target is not linked with an PP environment, dual-write, f&o apps virtual entities and data events concepts
are not applicable

• Target environment can be used imediatelly.

37
SCENARIO: Customer wants to copy a linked Power Platform environment to an unlinked Power Platform
environment. For example, when the customer wants to test a specific customer engagement apps case in an isolated
environment.

Action:
• Since the target is not linked with an f&o apps environment, dual-write, f&o apps virtual entities, etc. concepts are
not applicable

• Target environment can be used imediatelly.

Tip: You might consider removing the solutions specific to the Power Platform
integration

38
SCENARIO: Point in time restore in linked f&o apps environment and restore backup in linked Power Platform
environment

Action: Use the Point in time restore (PITR) option for f&o apps in LCS and Pattern:
Restore backup option for Dataverse in PPAC. Please note that for f&o apps a • Environment actions
PITR applies only to the database. such as copy or restore
After the two operations are completed and the code is aligned, the should be done in
environments should be ready for use. paralel for both PP
and f&o apps
Dual-write and virtual entity setup will revert to the status at the time of the
restore.
Anti-Patterns:
Business events and data events are also supported.* • Restoring the
environment only on
f&o apps (PITR for
*There are some pending items to be resolved for full support, please test carefully your scenario. database) or PP
(Restore backup)
Tip: Ensure that the PITR for f&o apps and restore for PPAC point to the same
timestamp.
If the restore is done separately, run all the steps from the database refresh/copy
scenario. Consider data re-alignment as well if dual-write has been leveraged.
39
SCENARIO: Change URL or Name in linked Power Platform environment.

Action: Leverage the Edit option in

Power Platform Admin Center

-> It is possible to change the name

-> It is not possible to change the URL

Tip: To avoid confusion, better to keep same name as in f&o apps and DV.

40
SCENARIO: A developer wants to work in a linked f&o apps environment (a Cloud Hosted environment) to test the
customizations done on dual-write, data events, etc.

Action: Anti-Patterns:
• At deployment of a
When creating the cloud-hosted Environment in LCS, choose Configure Power cloud-hosted
Platform integration.
environment, setting
Setting up the link with an existing PP environment as a post deployment the Configure Power
option is not possible for cloud-hosted environments. Platform integration
flag to No.

Tip: Treat development environments as disposable. Always test the developments in a

sandbox environment.

41
Scenario 1: New Finance and Operations & New Dataverse
implementation
1. Create f&o apps environment

• Create f&o apps environment and during deployment choose to not enable Power Platform Integration.

2. Create Dataverse environment & link with existing f&o apps

• Create Dataverse production environment and link with existing f&o apps env:
• via LCS using Setup button with the appropriate template
• via PPAC and then linked via LCS post f&o apps production environment. For this option, the Dataverse
environment created automatically without database at f&o apps environment deployment can be deleted if not
needed.

3. If Dual-write is in scope, complete setup

• In LCS, Click the ‘Link to Power Platform Integration’ button to enable dual-write for all legal entities or go to the
dual-write workspace and choose the legal entities.
• Install in Dataverse additional dual-write solutions that are required. In LCS, dual-write workspace, click on ‘Apply
solutions’ to bring in the table maps.
• If there is data from the f&o apps or Dataverse environment that needs to be synced, evaluate if initial sync can be
leveraged by consulting the initial sync guidance matrix. Consider alternative approach if data volumes are too high.
• Turn on table maps for live sync. here.

42
Scenario 2: New Finance and Operations & Existing Dataverse
implementation
1. Create f&o apps environment

• Create f&o apps environment and during deployment choose to not enable Power Platform Integration.

2. Connect existing f&o apps with existing Dataverse

• Use Setup button in LCS to connect the newly created f&o apps environment with the existing Dataverse environment.
Platform solutions for dual-write and virtual entities will be installed in Dataverse.
• After setup is completed, the Dataverse environment created automatically without database at f&o apps environment
deployment can be deleted if not needed.

3. If Dual-write is in scope for Dataverse, complete Setup

• In LCS, Click the ‘Dual-write application’ to install necessary solutions in Dataverse

• In LCS, click the ‘Link to Power Platform Integration’ button to enable dual-write for all legal entities or go to the dual-write
workspace and choose the legal entities.
• Install in Dataverse additional dual-write solutions that are required. In LCS, dual-write workspace, click on ‘Apply solutions’ to
bring in the table maps.
• For Dataverse follow the instructions to bootstrap existing data e.g. with company code
• If data from the Dataverse environment needs to be synced to f&o apps, evaluate if initial sync can be leveraged by consulting
the initial sync guidance matrix. Consider alternative approach if data volumes are too high.
• Turn on table maps for live sync

43
Scenario 3: Existing Finance and Operations & New Dataverse
implementation
1. Create Dataverse environment & Connect with f&o apps

• The Assumption is that Setup button is available (which means we choose No to enabling Power Platform Integration at F&O
apps env deployment). If setup button is not available, then an environment has already been created and it must be used
since the linking is irreversible.
• With Setup button available, we can create new Dataverse production environment and link with existing f&o apps env:
• via LCS using Setup button with the appropriate template
• via PPAC and then link the Dataverse environment via LCS using Setup button post f&o apps production environment. For
this option, the Dataverse environment created automatically without database at f&o apps environment deployment can be
deleted if not needed.

2.If Dual-write is in scope, complete setup

• In LCS, click the ‘Link to Power Platform Integration’ button to enable dual-write for all legal entities or go to the dual-write
workspace and choose the legal entities.
• Install in Dataverse additional dual-write solutions that are required. In LCS, dual-write workspace, click on ‘Apply solutions’ to
bring in the table maps.
• If data from f&o apps environment needs to be synced to Dataverse, evaluate if initial sync can be leveraged by consulting the
initial sync guidance matrix. Consider alternative approach if data volumes are too high.
• Turn on table maps for live sync

44
Deployment considerations for linked environments –Initial
Deployment from Pre-Prod to Prod
1. Prepare linked production Dataverse and f&o apps environments

• During, f&o apps prod deployment, choose to not enable Power Platform Integration.
• Dataverse production environment can be created:
• via LCS using Setup button with the appropriate template
• via PPAC and then linked via LCS post f&o apps production environment

2. Deploy code and move data from Pre-Prod to Prod environments

• For f&o apps prod environment, install the marked release candidate from Pre-Prod environment. Refresh Production database from Pre-
Prod environment. Dataverse environments must rely on deploying solutions from source control to get to be the accurate source of truth.
• Prod should always be a representation of what was deployed based on your source control system.

3. If Dual-write is in scope, complete Dual-write setup

• In LCS, click the ‘Link to Power Platform Integration’ button to enable dual-write for all legal entities. Afterwards, go to the dual-write
workspace and update the legal entities required. Install in Dataverse additional dual-write solutions that are required. In LCS, dual-write
workspace, click on ‘Apply solutions’ to bring in the table maps.
• If data needs to be synced between Dataverse and f&o apps, evaluate how initial sync can be leveraged by consulting the initial sync
guidance matrix. Consider alternative approach if data volumes are too high.
• Turn on table maps for live sync

4. If business events or data events are in scope they need to be rebuilt.

• Virtual entities from source environment will be copied over from the source.
• Business events and data events would need to be rebuilt
45
Deployment considerations for linked environments - Restore
Prod to Pre-Prod for testing new release
1. Prepare linked Pre-Prod Dataverse and f&o apps environments.

• If pre-prod environments don’t exist already, create and link environments as described in Scenario 1 (without needing initial
sync/data import)

2. Restore production environments over Pre-Prod environments.

• Move database from Prod to Pre-Prod in both environments

• Consider the data sensitivity and your internal compliance requirements.

5. Prepare and deploy new code

• Deploy the code version for the new release that needs to be tested.

3. Post restore, if dual-write is in scope, reset dual-write link.

• Post restore, ensure that table maps are stopped in dual-write workspace.
• Reset the Dual-Write link. If new solutions with table maps are installed, in LCS, dual-write workspace, click on ‘Apply solutions’
to bring in the table maps. Turn on table table maps without initial sync.

4. Post restore, if business events or data events are in scope they need to be rebuilt.

• Virtual entities from source environment will be copied over from the source.
• Business events and data events would need to be rebuilt
46
Resources
ODOP TechTalk Series https://aka.ms/odopTechTalks

One Admin – Implementation Scenarios https://aka.ms/OneAdminScenarios

Microsoft Power Platform integration with finance and operations apps - Finance & Operations

Dual-write home page - Finance & Operations

Virtual entities overview - Finance & Operations

Business events overview - Finance & Operations

Yammer : Dual-Write

Yammer : F&O with Power platform

Yammer : Business Events

Yammer : Data Management, Data Entities, OData and Integrations

Yammer : Microsoft Dynamics Lifecycle Services

47
Questions
Thank you!

48
Vocabulary / Terminology for PPAC and synonyms with LCS

Dataverse Database Enabled

Power Platform Environment Dynamics 365 Apps enabled

Power Platform Admin Center (PPAC) Store, manage, and share your organization's business data, apps, chatbots, and flows

Collaboration portal that provides an environment and a set of regularly updated

Lifecycle Services (LCS) services that can help you manage the application lifecycle of your implementations
of finance and operations apps

Dual-write is an out-of-box infrastructure that provides near-real-time interaction

Dual-write (DW) between customer engagement apps and finance and operations apps.

Finance and operations apps are a virtual data source in Dataverse, and enable
Virtual entities (VE) (CRUD) operations from Dataverse. By definition, the data for virtual entities doesn't
reside in Dataverse. Instead, it continues to reside in the app where it belongs

Data events are events that are based on changes to data in finance and operations
Data event (DE) apps. Create, update, and delete (CUD) events can be enabled for each entity.
database

Business events provide a mechanism that lets external systems receive notifications
Business Events (BE) from finance and operations applications

49