More updates

Author: KumarVivek

powerapps-docs/maker/common-data-service/data-platform-entity-licenses.md

@@ -1,11 +1,12 @@
 ---
 title: License requirements for entities| Microsoft Docs
-description: An explanation of license requirements for entities within Common Data Service.
-author: KumarVivek
+description: An explanation of license requirements for entities with complex business logic and restricted entities in Common Data Service.
+author: MicroSri
 ms.service: powerapps
 ms.topic: conceptual
-ms.date: 04/15/2020
-ms.author: kvivek
+ms.date: 08/28/2020
+ms.author: sriknair
+ms.reviewer: kvivek
 search.audienceType: 
   - maker
 search.app: 
@@ -15,22 +16,23 @@ search.app:
 
 # License requirements for entities
 
-App makers can use most of the entities available within Common Data Service (including custom entities and entities that are part of the Common Data Model) to create apps and flows for users who have a Power Apps or Power Automate license. In some cases, entities contain complex business logic or are tied to some Dynamics 365 apps that require app users to have a specific license. 
+App makers can use most of the entities available within Common Data Service (including custom entities and entities that are part of the Common Data Model) to create apps and flows for users who have a Power Apps or Power Automate license. 
 
-For the latest information on licensing requirements for entities, see the [Power Apps licensing guide](https://go.microsoft.com/fwlink/p/?linkid=2085130) 
+In some cases, entities contain complex business logic or are tied to some Dynamics 365 apps that require app users to have a specific license. This topic provides licensing information for entities with complex business logic and entities that are tied to Dynamics 365 apps (termed as restricted entities).
 
 ## Entities with complex business logic
 Entities that include the following complex server-side logic require users of an app or flow that uses these entities to have a Power Apps Plan 2 or Power Automate Plan 2 license:
 
-* Code plug-ins (for more information, see [Plug-in development](/powerapps/developer/common-data-service/plug-ins))
-* Real-time workflows (for more information, see [Workflow processes](/flow/workflow-processes))
+- Code plug-ins (for more information, see [Plug-in development](/powerapps/developer/common-data-service/plug-ins))
+- Real-time workflows (for more information, see [Workflow processes](/flow/workflow-processes))
 
     > [!NOTE]
     >  Only workflows that are converted to a real-time workflow are considered real-time and synchronous. Workflows that are run in the background can still be used with the appropriate Power Apps plan and do not require additional licenses.
 
-To know whether or not you added complex business logic to your entities, review the list of plug-in assemblies and workflows configured in your environment. For the list of entities which may contain server side logic after installing a model-driven application in Dynamics 365 (such as Dynamics 365 Sales or Dynamics 365 Customer Service), see [Complex entities requiring Power Apps Plan 2 licenses](data-platform-complex-entities.md)  
+To know whether or not you added complex business logic to your entities, review the list of plug-in assemblies and workflows configured in your environment. For the list of entities which may contain server side logic after installing a Dynamics 365 app (such as Dynamics 365 Sales or Dynamics 365 Customer Service), see [Complex entities requiring Power Apps or Power Automate licenses](data-platform-complex-entities.md)  
 
 ### Impacting license requirements when adding complex business logic
+
 App makers can add code plug-ins and real-time workflows to entities within Common Data Service, but doing so could change the license requirements for users of apps already deployed. App makers should be cautious when adding complex business logic to an entity and should first check which apps use the entity and whether users of those apps have the appropriate licenses.
 
 ## Restricted entities
@@ -48,22 +50,27 @@ Barb and Isaac are creating apps in Power Apps using Common Data Service to stor
 ### Entity creation
 
 -	No user can create a new restricted entity; Microsoft reserves the right to create and define them for Dynamics 365 apps (such as Dynamics 365 Sales or Dynamics 365 Customer Service)
+
 -	Users can create custom entities with Dynamics 365, Power Apps, or Power Automate license
--	For existing restricted entities, a user can add rows with the appropriate Dynamics 365 apps license
+
+-	For existing restricted entities, a user can add rows with the appropriate Dynamics 365 app license
 
 ### Create apps using Power Apps
 
 -	Barb and Isaac can create a canvas or model-driven app accessing restricted entities with a Dynamics 365 license
+
 -	Barb and Isaac can create a canvas or model driven app accessing custom entities with either Dynamics 365 or Power Apps license
 
 ### Use apps
 
 Barb wants to use two canvas apps:
 -	App 1 – uses the Appointment entity along with a custom entity that stores related information
+
 -	App 2 – uses the Appointment entity along with the Work Order entity, which is a restricted entity
 
 Isaac wants to use two model-driven apps:
 -	App 3 – uses the Appointment entity along with a custom entity that stores related information
+
 -	App 4 – uses the Appointment entity along with the Work Order entity, which is a restricted entity
 
 Barb and Isaac need the following licenses:
@@ -75,7 +82,21 @@ Barb and Isaac need the following licenses:
 
 -	Isaac can use App 4 only with a Dynamics 365 app license because there is a restricted entity accessed by the app.
 
- 
+### Create flows using Power Automate
+
+Now, let's see what happens when Isaac adds a real-time workflow to the custom entity that both Barb and Isaac are using in their apps.
+-	Isaac can create a workflow accessing restricted entities with a Dynamics 365 app license
+
+-	Barb and Isaac can create a workflow accessing custom entities with either Dynamics 365 app or Power Automate license 
+
+### Use flows
+-	Barb or Isaac can run the workflow accessing restricted entities with a Dynamics 365 app license
+
+-	Barb or Isaac can run the workflow accessing custom entities with either Dynamics 365 app or Power Automate license
+
 
 ## More about licensing
-For more information about Power Apps and Dynamics 365 licenses, see [Licensing overview](../../administrator/pricing-billing-skus.md).
+
+For more information about licensing, see [Licensing overview](/power-platform/admin/pricing-billing-skus).
+
+For the latest information on licensing requirements for entities, see the [Power Apps licensing guide](https://go.microsoft.com/fwlink/p/?linkid=2085130)