A company needs staff to query their own Microsoft 365 content, with no custom logic. What should you recommend first?
Why A is the answer
Microsoft 365 Copilot
Start with the prebuilt option when it meets the need. Custom builds are for gaps the product does not cover.
In detail
- Microsoft 365 Copilot already works over a user's Microsoft 365 content.
- No custom logic is needed.
- Measure what the prebuilt product misses before you plan a custom build.
Use case
An illustrative scenario, not a real incident.
A law firm wants staff to find past memos and emails. Microsoft 365 Copilot already searches that content within their permissions, so nothing needs building.
See it in different ways
flowchart TD
A{"Does a prebuilt option meet the need?"} -->|Yes| B["Buy: Microsoft 365 Copilot or a prebuilt agent"]
A -->|"Mostly"| C["Extend with an agent or connector"]
A -->|No| D["Build a custom agent"]stateDiagram-v2 [*] --> Requirement Requirement --> Copilot: Copilot already meets it Requirement --> Extend: Copilot needs your data or tools Requirement --> Build: needs its own logic Build --> CustomModel: existing models fail a measured need
flowchart TD
Q{"Does the product meet the need?"}
Q -->|"Yes"| A0["Use it as it is"]
Q -->|"Mostly"| A1["Extend it"]
Q -->|"No"| A2["Build custom"]Key point: Start with the prebuilt option.
Why the other options are wrong
- B. A new fine-tuned language model
- A fine-tuned model adds no access to their content.
- C. A Power Apps canvas app built from scratch
- A canvas app is a custom build for no reason.
- D. A custom multi-agent system in Foundry
- A custom system is far more than this needs.