Merge pull request #28926 from MicrosoftDocs/main

[AutoPublish] main to live - 07/14 10:32 PDT | 07/14 23:02 IST

Author: m365-skilling-repo-management[bot]

copilot/employee-self-service/customize.md

@@ -26,13 +26,13 @@ Customization is how you make the Employee Self-Service (ESS) agent work in the
 
 |Role |Activities to perform |Configuration area |
 |-----|----------------------|-------------------|
-|Environment Maker </br>Service owner of ESS agent |- Set up user context </br>- Customize ESS agent |Microsoft Copilot Studio |
+|Environment Maker </br>Owner of ESS agent |- Set up user context </br>- Customize ESS agent |Microsoft Copilot Studio |
 |ISV Administrators </br>Service owners of specific applications |Provide configuration inputs such as URLs, OAUTH tokens, and more |ISV configuration |
 |HR </br>IT </br>Legal </br>Privacy |-Identify knowledge sources </br>-Provide frequent queries </Identify sensitive queries> | N/A |
 
 ## Understanding components
 
-Before continuing with configuring the ESS Agent, the service owner who will manage the ESS agent going forward must have a thorough understanding of its architecture.  
+Before continuing with configuring the ESS Agent, the agent owner who will manage the ESS agent going forward must have a thorough understanding of its architecture.  
 The ESS agent is built with the following components:
 
 ### Topics

copilot/employee-self-service/deploy-overview-alm.md

@@ -80,7 +80,7 @@ You need to work with your organization’s Power Platform administrator to esta
 
 The ESS Agent has three distinct persona experiences:
 
-1. Administrator: Prepare the tenant to deploy, configure, and operate the ESS agent with the correct roles assigned to identified service owners.
+1. Administrator: Prepare the tenant to deploy, configure, and operate the ESS agent with the correct roles assigned to identified administrators.
 
 2. Environment maker: Install, configure, and publish the agent, including third-party ISV packages.
 

copilot/employee-self-service/prepare.md

@@ -36,7 +36,7 @@ Preparation is the first step to deploying the Employee Self-Service (ESS) agent
 1. Sign in as a Global admin to your [admin center](https://admin.microsoft.com).
 1. Select **Roles**, then choose **Role assignments**.
 1. In the **Microsoft Entra ID** section, find the **Power Platform Administrator** role.
-1. Add the users you've chosen as service owners for the ESS agent in the **Assigned** section.
+1. Add identified users in the **Assigned** section.
 
 ## Set up your Power Platform environment and assign the Environment Maker role
 
@@ -48,7 +48,7 @@ Preparation is the first step to deploying the Employee Self-Service (ESS) agent
     1. Add a **Dataverse data store**.
 1. Under **Access**, select **Security roles**.
 1. From the list of security roles, select **Environment Maker**. Choose **Members** in the top ribbon.
-1. Select **Add people** in the ribbon to add the designated person who can configure and publish the ESS agent. This person is typically the service owner in your organization.
+1. Select **Add people** in the ribbon to add the designated person who can configure and publish the ESS agent. This person is typically the agent owner in your organization.
 
 >[!NOTE]
 >Environment Makers can't install new agents. Only the environment administrators can install new agents.

copilot/employee-self-service/prerequisites.md

@@ -132,7 +132,7 @@ The ESS Agent includes several different technical components and configuration
 |-----|------------|---------------------|-------------------|
 |Global admin |User who has permissions to configure and delegate other roles |Assign user roles |Microsoft admin center |
 |Power Platform administrator |User who has power to configure Power Platform environments and assign roles within Power Platform |- Create environments </br> - Assign user roles </br> - Install ESS agent |- Power Platform </br> - Microsoft Copilot Studio |
-|Power Platform maker |User who has permission to make changes in a specific Power Platform environment. It’s recommended to have the service owner for this agent perform this role. |Configure ESS agent |- Power Platform </br> - Microsoft Copilot Studio |
+|Power Platform maker |User who has permission to make changes in a specific Power Platform environment. It’s recommended to have the agent owner for this agent perform this role. |Configure ESS agent |- Power Platform </br> - Microsoft Copilot Studio |
 |ISV administrators |Users who manage third-party solutions |Provide configuration inputs for ISV applications |ISV application's administration and configuration interface |
 |Information security |Infrastructure team who manage and control enterprise application security policies |- Allowlist inbound requests for ISV endpoints </br> - Manage single sign-on configurations |- Network firewall policies </br> - Signle sign-on applications |
 |Change control board |Team that manages changes in an organization relating to deploying an enterprise application |- Approve technical architecture </br> - Approve data security, compliance, and governance policies </br> - Approve responsible AI polices |N/A |

copilot/employee-self-service/publish.md

@@ -26,7 +26,7 @@ Publishing the Employee Self-Service (ESS) agent makes it available to your user
 
 |Role |Activities to perform |Configuration area |
 |-----|----------------------|-------------------|
-|Environment Maker/ Service owner of the ESS agent |- Deploy customization solution to target environment</br> - Set up authentication</br> - Publish ESS agent |Microsoft Copilot Studio |
+|Environment Maker/ Owner of the ESS agent |- Deploy customization solution to target environment</br> - Set up authentication</br> - Publish ESS agent |Microsoft Copilot Studio |
 |Administrator |- Approve the ESS publish request</br> - Deploy it to selected users |Microsoft admin center |
 |Business stakeholders/ champions |Identify test users |N/A |
 

copilot/employee-self-service/usage-analytics.md

@@ -24,7 +24,7 @@ appliesto:
 
 You can use different intefaces to monitor ESS agent usage depending on the role in your organization that is in charge of monitoring analytics.
 
-As an application or service owner with the Environment Maker role, you can view analytics in Copilot Studio by navigating to the **Analytics** tab.
+As an application or agent owner with the Environment Maker role, you can view analytics in Copilot Studio by navigating to the **Analytics** tab.
 
 For advanced reporting requirements, you can integrate Azure Application Insights with Copilot Studio to gather more telemetry.
 

copilot/employee-self-service/workday.md

@@ -228,10 +228,8 @@ In this article, you learn how to set up the **Microsoft Entra ID Integrated** a
 When installing the Workday connector, the first step is to set up connections using the form. Fill out the following fields:
 
 **Microsoft Entra resource URL (Application ID URI)**
-This is Microsoft Entra's app registration created for Workday SSO.
+This is Microsoft Entra's app registration created for Workday SSO. [Learn how to access app registrations](/entra/identity-platform/quickstart-register-app).
 
-1. Sign into the [Azure portal](https://portal.azure.com)
-1. In the search bar, search for **App registrations**.
 1. Select **All applications**.
 1. Choose the correct application created for Workday SSO.
 1. In the **Overview** section, use the **Application ID URI** under the **Essentials** tab.
@@ -266,6 +264,9 @@ Workday report configuration provides the SOAP base URL.
 |ISUAccount |PP environment variable |EmployeeContextRequestAccountName |ISU_WQL_COPILOT@< domain >.com |
 |ReportName |PP environment variable |EmployeeContextRequestReportName |WD_User_Context |
 
+>[!NOTE]
+>[If the ISUAccount name gets encoded in the report XML output, substitute %40 with @ character to make it a qualified UPN.]
+
 >[!IMPORTANT]
 >If the custom report name is different from the default name (**WD_User_Context**), follow these steps:
 
@@ -275,28 +276,34 @@ Workday report configuration provides the SOAP base URL.
 1. Select **Objects** > **Employee Self-Service Template Configuration** > **HRWorkdayHCMEmployeeGetContext**.
 1. Update the value with the correct name in the **Value** section.
 
+>[!NOTE]
+>[The ESS agent uses a new Workday connector, which is not the same as the one published in the Power Platfrom connectors list (Workday HCM - Connectors). The current connector used in the agent is Workday SOAP. Plan for any DLP policies to allowlist this connector in the environment where the agent is being deployed and tested.]
+
 #### Step four: Configure connections
 
 During the Workday Extension Pack installation process, you'll be prompted for the following connection configurations:
 
-|Connection reference name |Connection reference ID |Expected connection |
+|Connection reference name |Connection reference ID |Expected connection user account |
 |--------------------------|------------------------|--------------------|
-|OAuthUser |new_sharedworkdaysoap_ff0df |the signed-in user |
+|OAuthUser |new_sharedworkdaysoap_ff0df |Maker/the signed-in user |
 |Context Generic User |new_sharedworkdaysoap_d6081 |ISSG_WQL_COPILOT |
 |Generic User |new_sharedworkdaysoap_0786a |ISSG_Generic_COPILOT |
 |Microsoft Dataverse |msviess_sharedcommondataserviceforapps_92b66 |ISSG_WQL_COPILOT |
 
+Note that all the above user accounts mentioned in the table under "Expected connection user account" should be available in Entra for SSO and use the respective accounts in UPN format (example: `[email protected]`). Ensure that each connection is explicitly set up with its own account even though the connection status turned green after the first connection setup.
+
 #### Step five: Update the environment variables
 
 1. After you install the Workday extension, select **Solutions** in the left navigation in Copilot Studio.
 1. A banner on the solutions page prompts you to fill in the environment variables.
-1. Update the following environment variables:
+1. Update the following environment variables. Refer to the following inputs from the **SOAP Base URL** section.
 
 |Environment variable |Description |
 |---------------------|------------|
-|EmployeeContextRequestAccountName |Should contain the account that has access to the RaaS report. Reference from connection table: ISUAccount |
-|EmployeeContextRequestReportName |Should be the name of the report that contains the required information. Reference from connection table: Report Instance |
 |WorkdayWebsiteRedirectMessage |This is the message shown to users in success/failure scenarios for update email/phone number actions |
+|EmployeeContextRequestAccountName |Should contain the account that has access to the RaaS report. Reference from connection table: ISUAccount |
+|EmployeeContextRequestReportName |should be the name of the report that contains the required information reference from above connection table: ReportName |
+|EmployeeContextRequestReportInstanceName |should be the instance name that the report belongs to reference from above connection table: Report Instance |
 
 #### Step 6: Confirm the Workday flows are turned on
 

microsoft-365/admin/manage/assign-licenses-to-users.md

@@ -5,7 +5,7 @@ f1.keywords:
 author: cmcatee-MSFT
 ms.author: cmcatee
 manager: scotv
-ms.reviewer: sinakassaw, nicholak
+ms.reviewer: nicholak
 audience: Admin
 ms.topic: how-to
 ms.service: microsoft-365-business
@@ -32,7 +32,7 @@ ms.custom:
 - campaignIDs-batch1
 search.appverid: MET150
 description: "Learn how to assign or unassign licenses for your users in the Microsoft 365 admin center."
-ms.date: 04/07/2025
+ms.date: 07/08/2025
 ---
 
 # Assign or unassign licenses for users in the Microsoft 365 admin center

microsoft-365/admin/manage/manage-group-licenses.md

@@ -4,7 +4,7 @@ f1.keywords: NOCSH
 author: cmcatee-MSFT
 ms.author: cmcatee
 manager: scotv
-ms.reviewer: sinakassaw, nicholak
+ms.reviewer: nicholak
 audience: Admin
 ms.topic: how-to
 ms.service: microsoft-365-business
@@ -21,7 +21,7 @@ ms.custom:
 - m365-groups
 search.appverid: MET150
 description: "Learn how to assign or unassign licenses to groups in the Microsoft 365 admin center."
-ms.date: 04/07/2025
+ms.date: 07/08/2025
 ---
 
 # Assign or unassign licenses to a group in the Microsoft 365 admin center

microsoft-365/admin/misc/add-partner.md

@@ -5,7 +5,7 @@ f1.keywords:
 ms.author: cmcatee
 author: cmcatee-MSFT
 manager: scotv
-ms.reviewer: armanv, nicholak
+ms.reviewer: nicholak
 audience: Admin
 ms.topic: how-to
 ms.service: microsoft-365-business
@@ -28,7 +28,7 @@ search.appverid:
 - MOE150
 - GEA150
 description: "Learn how to add a partner of record when you buy Microsoft 365, change the partner, or delete a partner from a subscription."
-ms.date: 01/07/2025
+ms.date: 07/08/2025
 ---
 
 # Add, change, or delete a subscription advisor partner