wording changes

Author: daisyfell

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.