Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
As you consider using the Employee Self-Service Agent, we want to provide a clear view of release notes, known issues, and limitations—along with workarounds and roadmap visibility—to help you plan effectively and set the right expectations with your stakeholders.
Full list of release notes
Package versions are independent. Core, HR, and IT identify the Employee Self-Service base packages. ServiceNow integrations include the HR and IT packages for both ServiceNow HRSD and ITSM.
| Feature | Package versions | Update | Customer Action | Documentation | Status | Date |
|---|---|---|---|---|---|---|
| Rich Landing Page | Core: 1.2.0.4 HR: 1.1.0.5 IT: 1.1.0.6 ServiceNow integrations: 1.2.0.0 |
New customizable landing experience. | Optional configuration in the Microsoft 365 Admin Center. | Customize the Employee Self-Service agent | Available | Mar 2026 |
| Employee Self-Service on Mobile | Core: 1.2.0.4 HR: 1.1.0.5 IT: 1.1.0.6 ServiceNow integrations: 1.2.0.0 |
Employee Self-Service is now available on mobile devices. | No further set-up required. | Available | Mar 2026 | |
| Simplified Workday integration setup | Core: 1.2.0.4 HR: 1.1.0.5 IT: 1.1.0.6 ServiceNow integrations: 1.2.0.0 |
Reduces setup from four Power Platform connections to two. | Update the Workday package and configure the Workday REST base URL. | Set up the simplified Workday integration for Employee Self-Service | Available | May 2026 |
| Workday Reference Data Update (Get_References Removal) | Core: 1.2.0.4 HR: 1.1.0.5 IT: 1.1.0.6 ServiceNow integrations: 1.2.0.0 |
Removes the dependency on Workday's Get_References API. | Upgrade the Employee Self-Service base packages before the Workday package and update custom Reference IDs if needed. | Set up the simplified Workday integration for Employee Self-Service | Available | May 2026 |
| Stay Up to Date Proactive Ticketing Cards | Core: 1.2.0.4 HR: 1.1.0.5 IT: 1.1.0.6 ServiceNow integrations: 1.2.0.0 |
A new landing page capability that surfaces personalized, actionable updates as insight cards. | Enabled by default at GA. Admins can optionally disable it in the Microsoft 365 Admin Center. | Customize the Employee Self-Service agent | Available | June 2026 |
| Employee Self-Service GPT-5.5 model upgrade | SuccessFactors HR: 1.0.0.4 SuccessFactors IT: 1.0.0.6 Workday HR: 1.1.0.7 ServiceNow integrations: 1.2.0.0 Workday IT: 1.2.0.2 |
Upgraded from GPT-4.1 to GPT-5.5, a more advanced reasoning model. The built-in topic routing descriptions were also refreshed, so questions are routed to the correct topic more reliably. | Take the latest Employee Self-Service package to receive the GPT-5.5 update. Built-in topics update automatically. If you customized any Employee Self-Service topics, remove and reapply your customization to pick up the refreshed routing descriptions. | Available | July 2026 | |
| Microsoft Copilot Hub agent on GPT-5.5 | The Hub agent now supports GPT-5.5. Complete a one-time setup step for each connected agent so users don't get a duplicate reply (see Customer Action). | Add one setting to each connected agent under your Hub. This is a one-time step, and part of GPT-5.5 migration for existing customers: 1. Open your Hub agent in Copilot Studio and select the Agents tab. 2. For a connected agent, select Edit connection > ... > Open code view. 3. Add suppressPlannerResponse: true at the top level of the YAML, then select Save. 4. Repeat for every connected agent under your Hub. Skip any that don't reply to users directly. 5. Select Publish. Changes apply only after you publish. Agents reached directly, not through the Hub, aren't affected. |
Available | Aug 2026 |
Full list of known issues and limitations
| Area | Limitation | Planned fix | Workaround/Guidance |
|---|---|---|---|
| Model selection (GPT-5.3) | GPT-5.3 isn't supported. | Not applicable. | Don't select GPT-5.3. Select GPT-5.5 instead. |
| Model behavior (GPT-5.5) | Responses may take slightly longer with GPT-5.5 than with GPT-4.1. This is expected for a more advanced reasoning model and doesn't affect answer quality. | No fix required. This is expected behavior for a higher reasoning model. | No action required. |
| Model behavior (GPT-5.5) | For some ambiguous questions (for example in SuccessFactors or Workday), the agent may ask a clarifying question or answer from general knowledge instead of running the expected topic. | The built-in topic descriptions have been refreshed to improve this behavior and roll out with the update. | Take the latest Employee Self-Service package to receive the refreshed built-in topic descriptions. Built-in topics update automatically. If you customized any Employee Self-Service topics, remove and reapply your customization to pick up the refreshed routing descriptions. |
| Microsoft Copilot Hub agent (GPT-5.5) | Because the Hub orchestrates connected agents, a connected agent that replies on its own can produce a duplicate reply when the Hub runs on GPT-5.5. This is a behavior of the orchestration platform, not specific to Employee Self-Service. | A default-on platform update prevents the duplicate reply; no support request or feature flag is required. Enabling GPT-5.5 on the Hub also includes a one-time setup step for each connected agent. | Complete the Hub setup step in the release notes above: add suppressPlannerResponse: true to each connected agent under your Hub, then publish the Hub agent. For existing customers, this is a one-time step during GPT-5.5 migration. Reaching the Employee Self-Service HR or IT agent directly (not through the Hub) is unaffected. |
| External systems integration (Workday) | When you upgrade to the latest Workday integration, Employee Self-Service Workday topics may stop responding or return errors if the solution is upgraded in the wrong order or if tenant-specific reference data doesn't match the embedded configuration. - In some cases, all Workday prompts (for example, cost center, manager, phone update) may stop responding. - List or write operations may return empty/incorrect values or "Invalid Reference ID" errors if tenant reference IDs differ from the default configuration. |
Fixes are implemented in updated packages (including embedded reference data and improved configuration guidance), and rollout is ongoing. | - Ensure Employee Self-Service base packages are upgraded before the Workday package. - If prompts stop responding, turn the Employee Self-Service HR Workday cloud flow back on, then rerun the upgrade in the correct order. If list values or writes fail, update the reference data configuration to match your Workday tenant’s reference IDs. |
| External systems integration | Power Platform connectors can't be used with on-premises gateway connections at this time. | There are no plans to include this functionality in the future roadmap. | If needed, consider moving your key content to a cloud platform like SharePoint or ServiceNow. |
| External systems integration | Third-party connector setup (like Workday, ServiceNow, or SuccessFactors) takes time and typically needs someone with deep technical expertise. | By design - there are no plans to include it in the future roadmap. | To work around this behavior, carefully follow the setup documentation and involve someone with subject matter expertise in configuring third-party systems. Alternatively, consider starting with SharePoint as your initial knowledge source. You can add external system solution connectors once your IT team has the necessary expertise and capacity to manage the integration effectively. |
| Third-Party Identity Providers and Single Sign-on | Third-party identity providers (IdPs) and single sign-on (SSO) aren't fully evaluated for each of the configuration topologies. | We intend to address each configuration topology as they're reported. | Reach out to Microsoft support by submitting a support case when you encountered issues with third-party IdPs and/or SSO, so the product group can evaluate it. |
| Publishing | After you publish, it might take up to 48 hours for the Employee Self-Service agent to appear in Microsoft Copilot. | By design - there are no plans to include it in the future roadmap. | To skip the wait, download the manifest in Copilot Studio and upload it manually to Integrated Apps in Microsoft 365 Admin Center. Step-by-step guide. |
| Publishing | The agent doesn't automatically appear in Teams or Copilot after publishing. | By design - there are no plans to include it in the future roadmap. | Make sure the app is approved in Integrated Apps and assigned to the correct security group. For detailed instructions, refer to the publishing steps outlined in the deployment documentation. |
| Publishing | The agent currently functions only in the Copilot chat channel. The Teams app has open issues. | A fix is coming with roadmap updates. | As in Copilot Studio, both the Copilot chat and Teams channel are available as one option. Employee Self-Service agent is published to both channels. Users use the agent only in Copilot chat and don't deploy the agent in Teams in Copilot Agent publishing options, under the Microsoft admin center. |
| Publishing | Microsoft AutoUpdate for the Employee Self-Service agent and any external systems accelerator packages isn't supported. | A fix is coming with roadmap updates. | Makers are required to manually update both the Employee Self-Service agent core package and any associated external systems accelerator packages. |
| User Experience | The Employee Self-Service agent isn't supported yet on mobile devices. | Support for both mobile access is planned for release in 2026. | You can currently access the Employee Self-Service agent through the Microsoft 365 app on Android and iOS. However, some of the custom experience elements—like the official source badge, disclaimer, and certain visual features might not display as expected yet. We're actively working to improve how they appear on mobile phones. |
| User experience | You don't see the 'official source' badge when testing in Copilot Studio. | By design - there are no plans to include it in the future roadmap. | To see it live, publish the agent and try it in Microsoft Copilot. |
| User experience | The "Hello" topic isn't available by default and must be manually created and published as part of your Employee Self-Service agent setup. Without it, users might not receive a welcome message or clear guidance when they first interact with the agent. To ensure a smooth user experience, we recommend adding a custom "Hello" topic that introduces the agent, sets expectations, and explains what it can help with. | By design - there are no plans to include it in the future roadmap. | To ensure users have a smooth first interaction, create a custom topic that acts as your "Hello" or welcome message. You can name it something like "Welcome" or "Getting Started," and use trigger phrases such as "Hi", "Hello", or "Start". In the message, briefly explain what the Employee Self-Service agent can help with and how to ask questions. Publishing this custom topic replicates the behavior of a typical "Hello" experience and helps guide users from the start. |
| User experience | Agent names have length constraints, such as 42 characters maximum. | No plans – dependent on Copilot Studio. | Follow corporate naming conventions for agents that aren't long. |
| Workday/ServiceNow consent dialog appears for all users | When employees use the Employee Self-Service agent for the first time and the agent connects to external systems (for example, Workday or ServiceNow), a consent dialog may appear, asking the user to authorize the connection. This dialog requests permission to use the employee's credentials to retrieve data from those systems (for example, to execute SOAP operations in Workday). This dialog can appear for all users, even when the organization prefers to authorize on behalf of employees. End users must manually approve the consent to continue interacting with the agent, which may interrupt the experience or cause confusion. |
Currently, this setting isn't configurable directly within Copilot Studio. The only option is for support to disable this setting after a support ticket is filed. | Customers who prefer to disable this per-user consent prompt can request to have the feature disabled. To file this request: 1. Submit a support request through the Microsoft 365 admin center. 2. In your request, specify that you'd like to disable the Workday or ServiceNow consent dialog for the Employee Self-Service agent and authorize the connection on behalf of all users. 3. Once the request is received, Microsoft Support makes the change that allows tenant-level authorization. |
| Licensing and payment | Pay-as-you-go billing users (non-Microsoft Copilot license) can't access personal graph data (chat, emails, calendar, and so on), but can access tenant graph like SharePoint and Copilot connector (graph connectors) | By design – there are no plans to change this behavior in near roadmap | Plan suitable licensing for each scenario or persona to ensure employees can access the information they need. |
| Licensing and payment | Billing reports in Microsoft Admin Center (MAC) and Power Platform Admin Center (PPAC) always show the name of the agent matching with the name published in the app store. At this time, it's "Employee Self-Service-HR" and "Employee Self-Service-IT" - even if the maker renamed it in Copilot Studio. | By design – evaluating options with Platform teams to show the customized name for customers. | Coordinate with billing stakeholders communicating the agent's name to identify easily for any billing implications that might come up. |
| Licensing and payment | End users can continue consuming the Employee Self-Service agent when there's no Copilot license assigned to them and the billing plan is disabled, or the message capacity is exhausted. | End users can't consume the Employee Self-Service agent when the billing usage enforcement is rolled out by late summer 2025. | Enforce a billing plan in Copilot Studio per environment where the Employee Self-Service agent is being published. |
| Content related | Semantic indexing is limited to roughly 200 pages of content; anything beyond this limit isn't processed. | By design - there are no plans to include it in the future roadmap. | To stay within the ~200-page semantic indexing limit, consider breaking up your knowledge content into smaller, topic-focused libraries or SharePoint sites. Prioritize including only the most relevant and frequently used content in the initial knowledge source. Less critical or long-tail content can be stored separately and accessed through links or added later as needed. This configuration helps ensure the most valuable content is indexed and searchable by the Employee Self-Service agent. |
| Content related | If a page only has links and no actual content, it's not part of the summary the agent creates. | By design - there are no plans to include it in the future roadmap. | To ensure these pages are included in the summary, add a brief description or context alongside the links. Even a short paragraph explaining what the links are for or summarizing the content they point to can make the page eligible for summarization. This explanation helps the Employee Self-Service agent better understand and include the information during indexing. |
| Content related | You might notice lower-quality responses when the agent pulls information from Graph Connector content. | Enhanced response quality for Graph Connector content is planned for release in summer 2025. | To improve response quality, prioritize using SharePoint or directly integrated knowledge bases as your primary content sources, especially for high-impact topics. If you must use Graph Connector sources, ensure the content is well-structured, includes clear headings, and avoids overly long pages or lists of links. Adding short summaries or key takeaways at the top of each page can also help the agent generate better answers. |
| Relevance and user context | Employee Self-Service agent is unable to consistently apply profile data, like location, role, and company code, to give personalized and relevant responses. | In-progress on roadmap for improvement in 2026. | To improve response quality, prioritize adding as much user context in the prompt, such as, "What is the healthcare policy for full-time employees in Australia?" |
Platform dependency - known issues and limitations
- Power platform known issues
- Microsoft Dataverse - Connectors known issues
- Copilot Studio quotas and limits
- ServiceNow - Connectors
- ServiceNow Knowledge Microsoft Copilot connector
- SAP OData - Connectors
Tips for getting started smoothly
Validate configuration before you ship
Run FlightCheck to proactively validate your environment, connectors, DLP policy, and agent configuration. FlightCheck surfaces many of the publishing and integration issues called out earlier in this article before they reach end users.
Start with quick wins
Connector setup-especially for platforms like Workday and ServiceNow-often requires coordination between IT and HR. For faster time-to-value, start with knowledge retrieval from SharePoint and ServiceNow, which are easier to configure and deploy.
Get the right V-team in place
Employee Self-Service agent deployments move faster when you involve the right stakeholders early. Align your v-team across HR, IT, and Business Owners using this guidance to streamline decision-making and remove blockers.
Extend Employee Self-Service agent actions
The Employee Self-Service agent comes with out-of-the-box actions for common Human Capital Management (HCM) scenarios-such as checking time-off balances, accessing HR policies, or updating employee information. If you need more, follow our topic authoring guide to create and customize more topics that meet your organization's unique needs.