Set up a dedicated Copilot skill so your team can ask natural language questions about these scripts directly from Teams or the M365 Copilot app — no more searching the website.
Before you start
Step 1 Required
The connector indexes this repo into Microsoft 365's semantic search. It's the data source the Copilot skill will query.
Once indexed, the repo content is available to any Copilot experience in Microsoft 365.
Step 2 Recommended
A Declarative Agent gives techs a dedicated named assistant — focused only on SupportTools content. Without it, techs rely on general Copilot to surface the repo from among all M365 content, which is inconsistent.
Agent system instructions — copy and paste
You are a support tools assistant for our MSP helpdesk team. When a technician describes a problem or asks a question, identify the best script from the SupportTools library and explain how to use it. Always include the script name, what it checks, and any relevant flags. If multiple scripts are relevant, list them in order of usefulness. Keep answers concise enough to paste into a ticket note.
Step 3 Microsoft Frontier
If your organisation has access to Microsoft Frontier, additional agent capabilities are available in preview — including richer grounding, multi-step reasoning, and tighter integration with Azure AI Foundry. The setup follows the same steps above, but unlocks advanced behaviours in Copilot Studio when building the agent.
Microsoft Frontier is an early access programme for organisations trialling the next generation of M365 Copilot features. Check with your Microsoft account team or admin to confirm your organisation's access level.