Merge pull request #435 from MicrosoftDocs/master

11/4 Live Publish

Author: bishalgoswami

power-platform/admin/create-environment.md

@@ -93,18 +93,18 @@ To create an environment with a database, you need 1GB available database capaci
    |---------|---------|
    |Language     | The default language for this environment.        |
    |Currency     | The base currency used for reporting.         |
-   |Enable model-driven apps in Dynamics 365    | Select **Yes** and make a selection to automatically deploy apps such as Sales and Customer Service.      |
-   |Deploy sample apps and data     | Select **Yes** to include sample apps and data. Sample data gives you something to experiment with as you learn. You must select **No** for Enable model-driven apps in Dynamics 365 for this setting to appear.        |
+   |Enable Dynamics 365 apps | Select **Yes** and make a selection to automatically deploy apps such as Dynamics 365 Sales and Dynamics 365 Customer Service. See the next section, **Create an environment and add model-driven apps**.    |
+   |Deploy sample apps and data     | Select **Yes** to include sample apps and data. Sample data gives you something to experiment with as you learn. You must select **No** for **Enable Dynamics 365 apps** for this setting to appear.        |
    |Security group | Select a security group to restrict access to this environment. |
 
    > [!div class="mx-imgBorder"] 
    > ![](./media/new-environment-page2.png "Create new environment settings")
 
 ## Create an environment and add model-driven apps
-When you create an environment with a database, you can add model-driven apps in Dynamics 365, such as Dynamics 365 Sales and Customer Service.
+When you create an environment with a database, you can add model-driven apps in Dynamics 365 (such as Dynamics 365 Sales and Dynamics 365 Customer Service) to your environment.
 
 > [!NOTE]
-> Currently, apps can only be enabled for Production environments. You can create trials at [https://trials.dynamics.com](https://trials.dynamics.com/).
+> Currently, Dynamics 365 apps can only be enabled for Production environments. You can create Dynamics 365 app trials at <https://trials.dynamics.com>.
 
 ### Prerequisites
 To create an environment with a database, you need 1GB available database capacity.
@@ -132,7 +132,7 @@ To create an environment with a database, you need 1GB available database capaci
 
 4. Enter the language and currency settings.
 
-5. Set **model-driven apps in Dynamics 365** to **Yes**, and then select apps to include from the **Automatically deploy these apps** drop-down list.
+5. Set **Enable Dynamics 365 apps** to **Yes**, and then select apps to include from the **Automatically deploy these apps** list.
 
 6. Select **Save**.
 

power-platform/docfx.json

@@ -22,6 +22,7 @@
       {
         "files": [
           "**/*.png",
+          "**/*.svg",
           "**/*.jpg"
         ],
         "exclude": [

power-platform/index.yml

@@ -1,17 +1,18 @@
 ### YamlMime:Hub
 
 title: Microsoft Power Platform documentation # < 60 chars
+summary: Learn how to analyze data for insights, quickly and easily build custom apps, and automate workflows to improve business productivity with Power BI, PowerApps, and Power Automate.
 # brand: aspnet | azure | dotnet | dynamics | m365 | office | sql | windows | visual-studio | xamarin
 brand: dynamics
 
 metadata:
   title: Microsoft Power Platform documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
-  description: Learn how to deploy, customize, manage and use Microsoft Power Platform services and applications. Get documentation, sample code, tutorials, and more. # Required; article description that is displayed in search results. < 160 chars.
+  description: Learn how to analyze data for insights, quickly and easily build custom apps, and automate workflows to improve business productivity with Power BI, PowerApps, and Power Automate. # Required; article description that is displayed in search results. < 160 chars.
   ms.service: dynamics-365-crossapp #Required; service per approved list. service slug assigned to your service by ACOM.
   ms.topic: hub-page # Required
   author: buck1ey #Required; your GitHub user alias, with correct capitalization.
   ms.author: buckg #Required; microsoft alias of author; optional team alias.
-  ms.date: 10/01/2019 #Required; mm/dd/yyyy format.
+  ms.date: 10/29/2019 #Required; mm/dd/yyyy format.
   hide_bc: false
 
 # productDirectory section (optional)
@@ -20,43 +21,53 @@ productDirectory:
     # Card
     - title: Power BI
       # imageSrc should be square in ratio with no whitespace
-      imageSrc: /dynamics365/images/PowerBI_Mark_Yellow.svg
+      imageSrc: media/PowerBI_Mark_Yellow.svg
       links:
         - url: https://docs.microsoft.com/power-bi/
           text: Documentation
         - url: https://docs.microsoft.com/en-us/learn/browse/?products=power-bi
           text: Learn Power BI
     # Card
     - title: PowerApps
-      imageSrc: /dynamics365/images/PowerApps_Mark.svg
+      imageSrc: media/PowerApps_Mark.svg
       links:
         - url: https://docs.microsoft.com/powerapps
           text: Documentation
         - url: https://docs.microsoft.com/en-us/learn/browse/?products=powerapps
           text: Learn PowerApps
     # Card
-    - title: Microsoft Flow
-      imageSrc: /dynamics365/images/Flow_Mark.svg
+    - title: Power Automate
+      imageSrc: media/Flow_Mark.svg
       links:
         - url: https://docs.microsoft.com/flow/
           text: Documentation
         - url: https://docs.microsoft.com/en-us/learn/browse/?products=flow
-          text: Learn Microsoft Flow
+          text: Learn Power Automate
 
 additionalContent:
   # Supports up to 3 sections
   sections:
     - title: Related features
       items:
         # Card
+        - title: Common Data Service
+          summary: "Powerful data service and app platform to quickly build enterprise-grade apps with automated business processes"
+          url: https://docs.microsoft.com/powerapps/maker/common-data-service/data-platform-intro
+        # Card
         - title: AI Builder
           summary: "Enhance your apps and business processes with AI that’s easy to build and configure"
           url: https://docs.microsoft.com/ai-builder
         # Card
         - title: Common Data Model
           summary: "Unify data across all your business processes and enable interoperability among apps"
           url: https://docs.microsoft.com/common-data-model/
+    - title: See also
+      items:
         # Card
         - title: Dynamics 365
           summary: "The next generation of CRM and ERP applications"
-          url: /dynamics365/index
+          url: /dynamics365/index
+        # Card
+        - title: Microsoft Azure
+          summary: "Ever-expanding set of cloud computing services to help your organization meet it's business challenges"
+          url: https://docs.microsoft.com/en-us/azure

power-platform/media/Flow_Mark.svg

@@ -36,9 +36,9 @@
      href: how-to-test-bot.md
    - name: Work with variables
      href: how-to-variables.md
-   - name: Hand off a bot conversation to a live agent
+   - name: Trigger hand-off to a live human agent
      href: how-to-handoff.md
-   - name: Configure hand off with Omnichannel
+   - name: Configure hand off to Omnichannel for Customer Service
      href: configuration-hand-off-omnichannel.md
    - name: Add actions to your bot using Power Automate
      href: how-to-flow.md

power-platform/media/PowerApps_Mark.svg

@@ -1,5 +1,5 @@
 ---
-title: "Configure handoff with Omnichannel for Customer Service"
+title: "Configure hand-off to Omnichannel for Customer Service"
 description: "Have human agents intercede in bot conversations by connecting Power Virtual Agents to Omnichannel."
 ms.date: 10/30/2019
 ms.service:
@@ -13,25 +13,25 @@ ms.collection: virtual-agent
 ms.custom: handoff
 ---
 
-# Configure seamless and contextual hand-off to Omnichannel
-With Power Virtual Agents, you can seamlessly and contextually hand off escalated Power Virtual Agents conversations to live agents using [Omnichannel for Customer Service](https://docs.microsoft.com/dynamics365/omnichannel/omnichannel-customer-service-guide). 
+# Configure seamless and contextual hand-off to Omnichannel for Customer Service
+With Power Virtual Agents, you can seamlessly and contextually hand off escalated Power Virtual Agents conversations to live (human) agents using [Omnichannel for Dynamics 365 Customer Service](https://docs.microsoft.com/dynamics365/omnichannel/omnichannel-customer-service-guide). 
 
-When you hand off a conversation, you share the full history of the conversation (the context) as well as all user-defined variables. This allows Omnichannel to route incoming escalations to the right live agent queue and enables engaging live agents to review context from the prior conversation and resume the conversation.
+When you hand off a conversation, you share the full history of the conversation (the context) as well as all user-defined variables. This allows Omnichannel for Customer Service to route incoming escalations to the right live agent queue and enables engaging live agents to review context from the prior conversation and resume the conversation.
 
 For more information about hand off, and how to use hand-off within a bot conversation, see the [Using Transfer to agent node](how-to-handoff.md) topic.
 
 ## Pre-requisites
-* Product license: You need [product licenses for both Power Virtual Agents](https://go.microsoft.com/fwlink/?LinkId=2092080&clcid=0x409) and [Omnichannel for Customer service](https://docs.microsoft.com/dynamics365/customer-engagement/omnichannel/try-chat-for-dynamics365).
-* Role: You must be an [Omnichannel Administrator](https://docs.microsoft.com/dynamics365/customer-engagement/omnichannel/administrator/add-users-assign-roles) in Omnichannel.
-* Azure Application ID: You will need an [application registered in Azure](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#create-an-azure-active-directory-application) prior to connecting to Omnichannel.
+* Product license: You need a [product license for Power Virtual Agents](https://go.microsoft.com/fwlink/?LinkId=2092080&clcid=0x409) and [a product license for Omnichannel for Customer service](https://docs.microsoft.com/dynamics365/customer-engagement/omnichannel/try-chat-for-dynamics365).
+* Role: You must be an [Omnichannel for Customer Service Administrator](https://docs.microsoft.com/dynamics365/customer-engagement/omnichannel/administrator/add-users-assign-roles) in Omnichannel for Customer Service.
+* Azure Application ID: You will need an [application registered in Azure](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#create-an-azure-active-directory-application) prior to connecting to Omnichannel for Customer Service.
 
 
 ## Configure hand-off in the Power Virtual Agents app
 
-Sign in to the Power Virtual Agents instance you want to connect to Omnichannel.
+Sign in to the Power Virtual Agents instance you want to connect to Omnichannel for Customer Service.
 
 
-1. Select **Settings** then **Transfer to agent**.
+1. Select **Settings**, and then **Transfer to agent**.
 
     ![IMAGE SHOWING SETTINGS PANEL OPENED](media/handoff-settings.png)
 
@@ -41,43 +41,49 @@ Sign in to the Power Virtual Agents instance you want to connect to Omnichannel.
     ![IMAGE SHOWING OC TILE IN SETTINGS](media/handoff-oc-tile.png)
 
 
-1. Select **Next** to acknowledge the privacy policy. 
+1. To acknowledge the privacy policy, select **Next**. 
     >[!CAUTION]
-    >Ensure that you are adhere to [data sovereignty](data-location.md) laws when configuring this integration as your bot will store and send user information to your Omnichannel instance.
+    >Ensure that you adhere to [data sovereignty](data-location.md) laws when you configure this integration as your bot will store and send user information to your Omnichannel for Customer Service instance.
 
 1. Follow the steps to create or reuse an existing Azure application ID. Copy the *Application (client) ID* and paste it in the text box provided.
 
-1. Power Virtual Agents uses a [Teams channel](getting-started-deploy.md) to communicate with Omnichannel. If a Teams channel is not enabled, a Teams channel will be enabled when you select **Next**. 
+1. Power Virtual Agents uses a [Teams channel](getting-started-deploy.md) to communicate with Omnichannel for Customer Service. If a Teams channel is not enabled, a Teams channel will be enabled when you select **Next**. 
 
-1. Select the environment where your Omnichannel instance is provisioned.
-
-1. Select the **Go to Omnichannel** link to [continue configuring the bot connection in Omnichannel](https://docs.microsoft.com/dynamics365/omnichannel/administrator/configure-bot-virtual-agent).
+1. Select the environment where your Omnichannel for Customer Service instance is provisioned.
 
+1. Select the **Go to Omnichannel** link to [continue configuring the bot connection in Omnichannel for Customer Service](https://docs.microsoft.com/dynamics365/omnichannel/administrator/configure-bot-virtual-agent).
 
+<!--
 >[!NOTE]
 >If you see an error, review the possible [errors and mitigations listed below](#mitigations-for-known-issues).
+-->
+
 
 >[!NOTE]
 >Your bot must be in a published state for end-to-end capabilities to work as expected. Ensure that you have [published your bot](getting-started-deploy.md) prior to validating the integrated experience.
 
 ## Mitigations for known issues
+If you experience issues, see below for possible mitigations.
+<!--note from editor: We don't have headings without content underneath them, so I added a sentence. Feel free to make it better. 
+It's also worth asking if the info should go in a KB instead of product documentation. What you have below looks like it should go in a readme, but I'm not aware of one being done where you could add this. -->
 
-## Remove Omnichannel connection
-Once your bot has been connected to Omnichannel, you cannot remove the connection setting at this time. If you erroneously connected to the wrong Omnichannel instance or environment, you will need to create a new bot and try connecting to Omnichannel again.
-
-### Specific content doesn't appear in Omnichannel
-Some content may not show, such as emojis and certain types of notes or variables. If you encounter problems with the display of content, see the [Omnichannel documentation library for more details](https://docs.microsoft.com/dynamics365/omnichannel/omnichannel-readme).
+### Remove Omnichannel for Customer Service connection
+Once your bot has been connected to Omnichannel for Customer Service, you cannot remove the connection setting. If you erroneously connected to the wrong instance or environment, you will need to create a new bot and try connecting to Omnichannel for Customer Service again.
 
+### Specific content doesn't appear in Omnichannel for Customer Service
+Some content may not show, such as emojis and certain types of notes or variables. If you encounter problems with the display of content, see the [Omnichannel for Customer Service documentation library](https://docs.microsoft.com/dynamics365/omnichannel/omnichannel-readme).
 
 
+<!--
 ### Known connection error codes and mitigations
 Here are some known errors.
 
 | Error | Description | Next steps / Mitigation |
 | ------- | ------- | ------- |
 | 
 
->[!WARNING]
-><span style="background-color:yellow;">What errors are there?</span>
 
 For errors not shown here, please reach out to your dedicated Microsoft support contact.
+-->
+
+[!INCLUDE [handoff-known-limitations](includes/handoff-known-limitations.md)]