[Dev-Docs AI Improvement]: Microsoft 365 Agents Playground #13908
Conversation
Acrolinx ScorecardsWe currently enforce a minimum score of 80. Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:
More info about Acrolinx Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit ac206f2: 💡 Validation status: suggestions
msteams-platform/toolkit/debug-your-agents-playground.md
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
|
|
||
| > [!NOTE] | ||
| > | ||
| > Microsoft 365 Agents Playground (previously known as Teams App Test Tool) is available in the latest prerelease version of Microsoft 365 Agents Toolkit (previously known as Teams Toolkit). Ensure that you install the [latest prerelease version](install-Teams-Toolkit.md#install-a-prerelease-version) of Agents Toolkit. |
| ### Update the configuration file | ||
|
|
||
| If your bot code uses Bot Framework APIs, you can modify the configuration file to customize the API responses. For example, consider an Azure DevOps notification bot installed in a team that fetches inactive bugs from Azure DevOps. It identifies the owners of the inactive bugs, retrieves their email addresses, and sends daily notifications to their personal chats. | ||
| If your bot code utilizes Bot Framework APIs, you can modify the configuration file to customize the API responses. For instance, consider an Azure DevOps notification bot installed in a team that retrieves inactive bugs from Azure DevOps. It identifies the owners of these inactive bugs, retrieves their email addresses, and sends daily notifications to their personal chats. |
There was a problem hiding this comment.
If your bot code uses is better, rest you can use the new version
| To thoroughly test this bot in Agents Playground, ensure you update the configuration file with the correct email addresses of the inactive bug owners. | ||
|
|
||
| 1. Go to the `.m365agentsplayground.yml` file in the project's root folder. | ||
| 1. Navigate to the `.m365agentsplayground.yml` file in the project's root folder. |
There was a problem hiding this comment.
MSTP prefers Go to vs navigate - simple verbs
| 1. Navigate to the `.m365agentsplayground.yml` file in the project's root folder. | ||
|
|
||
| 1. Go to the `users` section and update the `name`, `userPrincipleName`, and `email` of the required user. | ||
| 1. Locate the `users` section and update the `name`, `userPrincipleName`, and `email` of the required user. |
There was a problem hiding this comment.
original version is prefered
This PR updates the content of the file: msteams-platform/toolkit/debug-your-agents-playground.md.
Submitted by: @yashy797