PlanSource

Title: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online User impact: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online. More info: When users attempt to create a SharePoint knowledge agent using Copilot in SharePoint Online, they may receive an error that states, “We couldn't verify your license.” Current status: We're continuing to monitor the rate of the deployment's progression through the impacted environment in an effort to establish a timeline for remediation. We'll aim to provide an update on this when possible. Scope of impact: Any user attempting to create SharePoint knowledge agents using Copilot in SharePoint Online may be affected. This information may be updated as our investigation continues. Root cause: A recent service change had a missing configuration that's preventing the licensing from being fetched and validated, causing impact. Next update by: Wednesday, October 28, 2026, at 7:00 PM UTC

The migration of Timesheets, Capacity Planner, and Financial Manager to Forge: https://www.tempo.io/product-news/tempo-moves-to-forge is underway, but the automatic rollout did not start on March 31, 2026 as planned. The automatic migration to Forge is tentatively scheduled to begin on June 15, 2026. You have the option to do either of the following: • Perform a manual update Review the expected changes (see links below) and assess any impacts to your workflows. If the impact is manageable, we recommend updating manually to control the timing of your instance’s migration. • Wait for automatic update The automatic rollout will occur gradually, so we are unable to confirm the exact date your instance will be updated. It will not be possible to schedule, delay, or opt out once started. After your instance is updated, you will receive an in-app notification confirming the change. You can also verify if your instance has migrated to Forge by checking the app versions: https://tempo-io.atlassian.net/wiki/spaces/DRAFTTIMESHEETS/pages/5679415354/Timesheets+Migration+to+Forge+FAQs#How-to-Check-Your-Current-Version. Breaking changes Most of the migration is seamless, but a few things will change that may affect you, particularly around JQL filters: • JQL filter syntax – issueInternal, Account, Tempo Team, and custom field IDs • Tempo Panels in Jira issue view • Keyboard shortcuts • OAuth app URLs Please review the relevant documentation to prepare for changes that might affect you: • Expected Changes in Timesheets on Forge: https://help.tempo.io/timesheets/latest/expected-changes-in-timesheets-on-forge • Expected Changes in Capacity Planner on Forge: https://help.tempo.io/planner/latest/expected-changes-in-capacity-planner-on-forge • Expected Changes in Financial Manager on Forge: https://help.tempo.io/financialmanager/latest/expected-changes-in-financial-manager-on-forge