Forum Widgets
Latest Discussions
Guidelines silently bypassed when product knowledge is unavailable
With saved and active guidelines in place — locale en-GB, minimum word count, mandatory signature, AI disclaimer, unsubscribe text, no bullet points, no unevidenced outcome claims — the agent produced a draft that breached all of them, using American spelling, describing a consultancy as "our platform", omitting the signature and disclaimer entirely, and implying results achieved for other customers. The agent explained this as fallback logic ignoring some constraints because the product knowledge context was missing. Expected: where required context is unavailable, generation fails or warns. Actual: generation proceeds against a default template, silently dropping configured constraints, including accuracy and compliance guardrails. Impact: a fallback path that discards compliance settings is more dangerous than one that fails, because the output looks complete and passes casual review. Guardrails that only apply when context happens to load are not guardrails. Suggestion: treat locale, disclaimer, unsubscribe text and accuracy constraints as non-bypassable, independent of knowledge availability. Where context is missing, block generation rather than substituting a default.Sales agent guideline and product knowledge changes reported as saved but not persisted
Configuring a sales agent in Frontier, several settings were confirmed by the agent as saved and active, but were absent on subsequent readback. Observed over a single configuration session: Product knowledge was confirmed as added in detail on two occasions. A later full readback showed no stored product knowledge sources at all. The email signature was reported as updated four times. Each attempt returned a different malformed value: a stray literal "Text" prefix outside the paragraph tag, raw line breaks instead of <br>, and on one attempt a dropped ampersand. The Redirect stage was reported as existing, then as not existing, then appeared again in the playbook stage list with no guidelines attached. Expected: settings confirmed as saved persist, and readback reflects stored state accurately. Actual: the agent's own report of its configuration state could not be relied upon, so every change required manual verification. Where product knowledge was silently absent, generated output fell back to generic content. Impact: there is no trustworthy way to confirm which configuration is in force at send time. For any customer-facing agent this is a blocker to go-live, since output cannot be assured against approved messaging. Suggestion: expose a single authoritative configuration readback showing stored values verbatim, and surface provisioning state clearly where content is still being ingested. Or, enable manual editing of agent setup config rather than requiring agent to update it.
Sales Agent for Copilot Chat - PPLAT DLP Policy
We are working on setting up the Sales Agent for Copilot Chat. The goal is to have it interact with Salesforce. We are aware that the Salesforce connector is required in the DLP policy for the environment "msdyn_viva". Does anyone know what other Microsoft connectors should or are recommended be approved in the Business category of the DLP policy? Not finding any documentation on this. https://learn.microsoft.com/en-us/microsoft-sales-copilot/landing
Endless spinner in Copilot Sales Outlook App after login to Salesforce
We are experiencing an issue with the Copilot Sales App in Outlook. Users are launching the app and authenticate to Salesforce successfully. Then, a message saying "Sales is loading..." is shown with a spinner and nothing happens, no matter how long you wait. This only happens to some users and not to all users. Sometimes it happens to users who were previously able to load the app fine.
Copilot For Sales - Dynamics Environment Switching
Hello, We have 2 dynamics environments we've been using for the Copilot for Sales Roll-out (UAT and Production). We've currently deployed into Production and onboarded our Sales Team users. As an admin, I would like to switch my environment back to UAT to complete some customisation testing in our UAT environment, before I roll it out in Production. If I switch the environment from my account (as an Admin) from Prod to UAT. Is there any knock-on effect for other users? Will it affect the configuration I've already set-up? We currently have 2 full admins for Copilot for Sales, the other admin would stay in Production. Any guidance is appreciated. Kind regards, Adam
Microsoft FastTrack Agent community
Hello BANNEDUSERNAME copilot for sales discussion group If you are an enterprise or majors customer using Copilot for Sales or Sales in M365 and would like to meet more like-minded customers as well as speak with FastTrack subject matter experts on a bi-monthly basis, get product roadmap updates and provide feedback to the product team, then please fill out the D365 Agent Deployment Program and Agent Community - Customer Registration – Fill out form or use the QR Code below to provide us with your permission to send you an invitation to the Microsoft Agent community. The AI Adoption team for pre-built agents for business applications would be thrilled to have you join us! The community also offers an online forum for discussions and Q&A. Thank you and we look forward to hearing from you! Microsoft, Dynamics 365 Agent Deployment team
Copilot doesn't add a column to the matrix visual
I have a sales report that I would like to add a column to. I am trying out Copilot, and it cannot add the column in the matrix visual, even with the prompt I give it. If it can generate reports, why can't Copilot add a column when I ask it to? Example: Need to add a SKU column, which is on the semantic model in this matrix visual, but it says the following: I attempted to add the SKU field from the Sales & Sold Returns table to your matrix visual, placing it after Product Brand and before Item Name. However, the update did not succeed—SKU is still not appearing in the matrix. This may be due to a limitation in the current visual configuration or a technical restriction. Please verify that the SKU field is not already present elsewhere in the matrix, and that there are no restrictions on adding it. If you need further troubleshooting or want to try a different approach, let me know how you’d like to proceed.
