Merge pull request MicrosoftDocs#4724 from MicrosoftDocs/master

updating working

Author: mduelae

.openpublishing.redirection.json

@@ -6279,6 +6279,11 @@
       "source_path": "powerapps-docs/developer/data-platform/developer-resources-page.md",
       "redirect_url": "/powerapps/developer/data-platform/view-download-developer-resources",
       "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/maker/data-platform/business-events.md",
+      "redirect_url": "/powerapps/developer/data-platform/business-events",
+      "redirect_document_id": "false"
     }
   ]
 }

powerapps-docs/developer/data-platform/TOC.yml

@@ -159,6 +159,8 @@
         href: org-service/samples/web-access-plugin.md
   - name: Workflow extensions
     href: workflow/workflow-extensions.md
+  - name: Business Events (preview)
+    href: business-events.md
   - name: Scalable customization design
     href: scalable-customization-design/overview.md
   - name: Best Practices
@@ -217,7 +219,6 @@
       href: walkthrough-configure-azure-sas-integration.md
     - name: "Tutorial: Register an Azure-aware plug-in using the Plug-in Registration Tool"
       href: walkthrough-register-azure-aware-plug-in-using-plug-in-registration-tool.md
-
     - name: "Tutorial: Update a service endpoint imported from a solution"
       href: walkthrough-update-service-endpoint-imported-solution.md
   - name: Use Web Hooks
@@ -393,7 +394,7 @@
       href: authenticate-dot-net-framework.md
     - name: Use OAuth
       href: authenticate-oauth.md
-    - name: Use Microsoft 365 (WS-Trust)
+    - name: Use Office365 (WS-Trust)
       href: authenticate-office365-deprecation.md
   - name: "Tutorial: Register an app with Azure Active Directory"
     href: walkthrough-register-app-azure-active-directory.md
@@ -458,4 +459,4 @@
   - name: Customization solutions file schema
     href: customization-solutions-file-schema.md
   - name: FetchXML schema
-    href: fetchxml-schema.md
+    href: fetchxml-schema.md

powerapps-docs/developer/data-platform/authenticate-office365-deprecation.md

@@ -1,6 +1,6 @@
 ---
-title: "Use Microsoft 365 authentication with Microsoft Dataverse (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "Describes deprecation of the WS-Trust security protocol and the code changes required in applications that use Microsoft 365 authentication."
+title: "Use Office365 authentication with Microsoft Dataverse (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+description: "Describes deprecation of the WS-Trust security protocol and the code changes required in applications that use Office365 authentication."
 ms.custom: ""
 ms.date: 03/23/2021
 ms.reviewer: "pehecke"
@@ -16,7 +16,7 @@ search.app:
   - D365CE
 ---
 
-# Use Microsoft 365 authentication with Microsoft Dataverse
+# Use Office365 authentication with Microsoft Dataverse
 
 Use of the WS-Trust authentication security protocol when connecting to Microsoft Dataverse is no longer recommended and has been deprecated; see the [announcement](/power-platform/important-changes-coming#deprecation-of-office365-authentication-type-and-organizationserviceproxy-class-for-connecting-to-common-data-service).
 
@@ -54,8 +54,7 @@ using (OrganizationServiceProxy organizationServiceProxy =
 ## What should I do to fix my application code if affected?
 
 There are very straight forward ways to modify your application’s code to use
-the recommended connection interface for authentication with Common Data
-Service.
+the recommended connection interface for authentication with Dataverse.
 
 - If your code uses an [Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy](/dotnet/api/microsoft.xrm.sdk.client.organizationserviceproxy) instance:
 
@@ -79,9 +78,9 @@ Service.
     Password=passcode;Url=https://contosotest.crm.dynamics.com;AppId=51f81489-12ee-4a9e-aaae-a2591f45987d;
     RedirectUri=app://58145B91-0C36-4500-8554-080854F2AC97;LoginPrompt=Auto"`
 
-        This will be your fastest way to update the code. Note that LoginPrompt can be set to “never” to simulate the way that the Microsoft 365 behavior worked.
+        This will be your fastest way to update the code. Note that LoginPrompt can be set to “never” to simulate the way that the Office365 behavior worked.
 
-        The AppId and RedirectUri provided above are examples of working application registration values. These values work everywhere our online services are deployed. However, they are provided here as examples and you are encouraged to create your own application registration in Azure Active Directory (AAD) for applications running in your tenant.<p/>
+        The AppId and RedirectUri provided above are examples of working application registration values. These values work everywhere our online services are deployed. However, they are provided here as examples and you are encouraged to create your own application registration in Azure Active Directory (Azure AD) for applications running in your tenant.<p/>
 
     - When we announce it, update to the latest [Microsoft.CrmSdk.XrmTooling.CoreAssembly](https://www.nuget.org/packages/Microsoft.CrmSdk.XrmTooling.CoreAssembly/) NuGet package that includes auto redirect support. This library will redirect an authentication type of Office365 to OAuth and use the example AppId and Redirect URI automatically. This capability is planned for the 9.2.x version of the Microsoft.CrmSdk.XrmTooling.CoreAssembly package.
 
@@ -98,4 +97,4 @@ To do this, you must first register the application user (Service Principal) in
 We will be monitoring the Power Apps ALM and ProDev community [forums](https://powerusers.microsoft.com/t5/Power-Apps-Component-Framework/bd-p/pa_component_framework). Please take a look there to get help on how to solve various issues or post a
 question.
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/best-practices/business-logic/develop-iplugin-implementations-stateless.md

@@ -5,6 +5,7 @@ services: ''
 suite: powerapps
 documentationcenter: na
 author: jowells
+ms.reviewer: phecke
 manager: austinj
 editor: ''
 tags: ''

powerapps-docs/maker/data-platform/business-events.md renamed to powerapps-docs/developer/data-platform/business-events.md

@@ -27,7 +27,7 @@ Automation of business logic and integration with other systems are driven by ev
 - Web Hooks
 - Dataverse plug-ins
 
-Dataverse has a robust event framework to capture system events *within* Dataverse. You can respond to events within the system using the Dataverse Event Framework. This isn't changing. More information [Event framework](../../developer/data-platform/event-framework.md)
+Dataverse has a robust event framework to capture system events *within* Dataverse. You can respond to events within the system using the Dataverse Event Framework. This isn't changing. More information [Event framework](event-framework.md)
 
 Dataverse Business events provides new ways to expose events and compose your business logic to respond to them asynchronously, such as the Power Automate Dataverse **When an action is performed** trigger.
 
@@ -51,7 +51,7 @@ Dataverse business events includes concepts from [Dynamics Finance and Operation
 
 ## Event Catalog
 
-To expose a business event it must be cataloged. More information: [Catalog and CatalogAssignment tables](../../developer/data-platform/catalog-catalogassignment.md)
+To expose a business event it must be cataloged. More information: [Catalog and CatalogAssignment tables](catalog-catalogassignment.md)
 
 A catalog makes it easier to discover the business event because they are grouped by the containing solution and categories defined for that solution. The solution publisher selects which events are most relevant for their solution.
 
@@ -78,15 +78,15 @@ If your solution consists of multiple dependent solutions, you may define the ro
 
 When a table is assigned to a category, certain operations bound to the table will be included. You can't select each operation individually. If the table supports Create, Update, and Delete operations, these events will be included.
 
-Additional events related to other operations will also be included. For example, if the table is user-owned it participates in security events. The owner of any record in the table will be able to share it, change sharing capabilities, or stop sharing the record. Operations related to sharing are exposed as `GrantAccess`, `ModifyAccess`, and `RevokeAccess` events. Additional events may also be included depending on the table. If the table is a Virtual Table, and it has been configured to support Virtual Table events, the `OnExternalCreated`, `OnExternalUpdated`, `OnExternalDeleted` events will be included. More information: [Enable Virtual Tables to support Dataverse events](../../developer/data-platform/virtual-entities/enable-virtual-table-event-support.md)
+Additional events related to other operations will also be included. For example, if the table is user-owned it participates in security events. The owner of any record in the table will be able to share it, change sharing capabilities, or stop sharing the record. Operations related to sharing are exposed as `GrantAccess`, `ModifyAccess`, and `RevokeAccess` events. Additional events may also be included depending on the table. If the table is a Virtual Table, and it has been configured to support Virtual Table events, the `OnExternalCreated`, `OnExternalUpdated`, `OnExternalDeleted` events will be included. More information: [Enable Virtual Tables to support Dataverse events](virtual-entities/enable-virtual-table-event-support.md)
 
 Add only those tables which contain business data that will be of interest to subscribers. You should not try to include every table.
 
 The same table can be included in multiple catalogs. For example, if your solution depends on customer data in the Dataverse Account or Contact tables, you should include them. Other catalogs may include tables from your solution.
 
 ## Custom Events
 
-Use Dataverse Custom API to create custom events. Each custom API will create a new Dataverse message and provide the web service endpoint to call the custom API. More information: [Create and use Custom APIs](../../developer/data-platform/custom-api.md).
+Use Dataverse Custom API to create custom events. Each custom API will create a new Dataverse message and provide the web service endpoint to call the custom API. More information: [Create and use Custom APIs](custom-api.md).
 
 Custom business events can only send notifications when an event is completed. Dataverse event framework provides capabilities to include synchronous logic which can cancel an operation or change the output so that you can extend the behavior of the system. Many of the same messages exposed with business events may be extended using synchronous logic in the Dataverse event framework, but business event notifications only occur when these operations complete successfully.
 
@@ -110,7 +110,7 @@ When you consider custom apis to catalog as business events in your solution use
 
 ### Custom Process Actions
 
-The concept of *Custom Action* includes both [Custom API](../../developer/data-platform/custom-api.md) and [Custom Process actions](../../developer/data-platform/workflow-custom-actions.md). They both create a new API, but how they do it is different. For custom business events, we recommend Custom API.
+The concept of *Custom Action* includes both [Custom API](custom-api.md) and [Custom Process actions](workflow-custom-actions.md). They both create a new API, but how they do it is different. For custom business events, we recommend Custom API.
 
 Custom process actions can also be cataloged as business events. This is for backward compatibility if your solution already uses custom process actions to encapsulate some business logic which would represent a business event. You are not required to migrate this custom action to use Custom API.
 
@@ -119,7 +119,7 @@ However, custom process actions have the following limitations:
 - Like any workflow, they can be disabled in the UI. You may not know when someone disables your custom process action until it suddenly stops working.
 - Until recently, there was no way to prevent synchronous plug-in steps to be registered on custom process actions, which means anyone could register synchronous steps that could change the behavior of the custom process action or even cancel it. There is now a [IsCustomProcessingStepAllowedForOtherPublishers](/reference/entities/workflow#BKMK_IsCustomProcessingStepAllowedForOtherPublishers) managed property that allows a custom process action to block this. But if you are going to update your custom process action to set this property, you should consider converting it to use Custom API instead.
 
-For more information about how they are different, see [Compare Custom Process Action and Custom API](../../developer/data-platform/custom-actions.md#compare-custom-process-action-and-custom-api)
+For more information about how they are different, see [Compare Custom Process Action and Custom API](custom-actions.md#compare-custom-process-action-and-custom-api)
 
 If your custom process action doesn’t contain any logic within the workflow designer and relies only on plug-ins to perform operations, you can probably migrate the custom process action to be a custom api to mitigate these issues. 
 
@@ -136,7 +136,7 @@ Custom APIs created for external events should align to these principles:
 
 - They should not have any plug-in type specified for the main operation.
 - They should not allow any synchronous step registrations. 
-    - The custom api [Allowed Custom Processing Step Type](/developer/data-platform/reference/entities/customapi#BKMK_AllowedCustomProcessingStepType) property should be set to **Async Only**. This will prevent any asynchronous steps from being applied for this API.
+    - The custom api [Allowed Custom Processing Step Type](/developer/data-platform/reference/entities/customapi#BKMK_AllowedCustomProcessingStepType) property should be set to **Async Only**. This will prevent any synchronous steps from being applied for this API.
 - They should not have any response properties, only request parameters.
     - With no synchronous logic, there is no way to set response properties.
 
@@ -165,22 +165,22 @@ The key requirement to use custom API to send business events is that your appli
 
 By removing all synchronous logic from the custom api the likelihood of an error causing the operation to fail is extremely low, but not impossible. Your calling application must provide a way to deal with transient errors in the event the Dataverse service isn’t responding, there are network connectivity issues, or service protection limit errors are returned.
 
-To enable authorized calls to Dataverse from your application there must be an Application user configured for the Dataverse environment. More information: [Build web applications using server-to-server (S2S) authentication](../../developer/data-platform/build-web-applications-server-server-s2s-authentication.md).
+To enable authorized calls to Dataverse from your application there must be an Application user configured for the Dataverse environment. More information: [Build web applications using server-to-server (S2S) authentication](build-web-applications-server-server-s2s-authentication.md).
 
 ## Use Business Events to trigger automation
 
 As business events becomes a common pattern, there will be multiple ways to enable automation.
 
 The first experience where business events are exposed is in Power Automate Dataverse connector using the [When an action is performed (preview)](/connectors/commondataserviceforapps/#when-an-action-is-performed-(preview)) trigger.
 
-:::image type="content" source="../../developer/data-platform/media/when-an-action-is-performed-trigger.png" alt-text="When an action is performed trigger":::
+:::image type="content" source="media/when-an-action-is-performed-trigger.png" alt-text="When an action is performed trigger":::
 
 Within this experience Create, Update, and Delete events are not shown for table events. These events are already available using the [When a row is added, modified or deleted](/connectors/commondataserviceforapps/#when-a-row-is-added,-modified-or-deleted) trigger.
 
 
 ## See Also
 
-[Catalog and CatalogAssignment tables](../../developer/data-platform/catalog-catalogassignment.md)<br />
-[Enable Virtual Tables to support Dataverse events](../../developer/data-platform/virtual-entities/enable-virtual-table-event-support.md)
+[Catalog and CatalogAssignment tables](catalog-catalogassignment.md)<br />
+[Enable Virtual Tables to support Dataverse events](virtual-entities/enable-virtual-table-event-support.md)
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/catalog-catalogassignment.md

@@ -18,7 +18,7 @@ search.app:
 
 # Catalog and CatalogAssignment tables
 
-Use the [Catalog](reference/entities/catalog.md) and [CatalogAssignment](reference/entities/catalogassignment.md) tables to create a structure to expose actions used in your solution as business events. Microsoft Dataverse Business events is a new capability currently being developed. Business events will enable many scenarios to create integrations with many applications through Dataverse. More information: [Microsoft Dataverse business events](../../maker/data-platform/business-events.md)
+Use the [Catalog](reference/entities/catalog.md) and [CatalogAssignment](reference/entities/catalogassignment.md) tables to create a structure to expose actions used in your solution as business events. Microsoft Dataverse Business events is a new capability currently being developed. Business events will enable many scenarios to create integrations with many applications through Dataverse. More information: [Microsoft Dataverse business events](business-events.md)
 
 Your catalog will describe those events that are relevant to your solution so that people can use them. If you do not catalog the events relevant to your solution, they may not be available to people using your solution.
 
@@ -500,7 +500,7 @@ For example:
 
 ### See also  
 
-[Microsoft Dataverse business events (preview)](../../maker/data-platform/business-events.md)<br />
+[Microsoft Dataverse business events (preview)](business-events.md)<br />
 [Create an entity record using the Web API](webapi/create-entity-web-api.md)<br />
 [Retrieve an entity record using the Web API](webapi/retrieve-entity-using-web-api.md)<br />
 [Create entities using the Organization Service](org-service/entity-operations-create.md)<br />

powerapps-docs/developer/data-platform/virtual-entities/enable-virtual-table-event-support.md

@@ -18,7 +18,7 @@ search.app:
 
 # Enable Virtual Tables to support Dataverse events
 
-You can allow Virtual entities to participate in asynchronous Dataverse Event Framework pipeline events and in the PowerAutomate Dataverse connector [When a row is added, modified or deleted](/connectors/commondataserviceforapps/#when-a-row-is-added,-modified-or-deleted) trigger. This capability is enabled as part of Dataverse business events. More information: [Microsoft Dataverse business events](../../../maker/data-platform/business-events.md)
+You can allow Virtual entities to participate in asynchronous Dataverse Event Framework pipeline events and in the PowerAutomate Dataverse connector [When a row is added, modified or deleted](/connectors/commondataserviceforapps/#when-a-row-is-added,-modified-or-deleted) trigger. This capability is enabled as part of Dataverse business events. More information: [Microsoft Dataverse business events (preview)](../business-events.md)
 
 Without any of the configuration described in this topic, most virtual entities do not participate in the Event Framework pipeline like other entities. This means you cannot register plug-in steps against Create, Update, and Delete (CUD) events that occur, and although CUD events appear for these entities in the Power Automate Dataverse connector, an error is thrown when people try to save a flow that uses them.
 
@@ -468,5 +468,5 @@ var service = new CrmServiceClient(conn);
 ## See Also
 
 [Event framework](../event-framework.md)<br />
-[Microsoft Dataverse business events](../../../maker/data-platform/business-events.md)<br />
+[Microsoft Dataverse business events (preview)](../business-events.md)<br />
 [Get started with virtual tables (entities)](get-started-ve.md)