Copilot FAQ & Troubleshooting

A: Copilot appears as a button or icon in the ribbon of Microsoft 365 apps. If you don't see it:

• Ensure you have a Microsoft 365 Copilot license assigned (contact IT if unsure)
• Check that you're using a supported app version (Copilot requires recent versions of Office apps)
• Try refreshing the app or signing out and back into Microsoft 365
• Verify your organization has enabled Copilot for your tenant

If you still don't see it, contact your IT department to verify license assignment and tenant configuration.

A: You should see a Copilot icon or button in the ribbon of Word, Excel, PowerPoint, Outlook, and Teams. In Teams, Copilot appears in the chat interface. If you're unsure, check with your IT department or look for the Copilot icon (usually a sparkle or chat bubble icon) in your Office apps.

A: No. Copilot respects the same permissions as you do. It can only access files and information that you have permission to view. This is a security feature—Copilot operates within your Microsoft 365 tenant and respects all existing access controls, SharePoint permissions, and data loss prevention policies.

A: This usually happens when Copilot doesn't have access to the right source files. To fix this:

• Attach source files: Always attach the documents, spreadsheets, or emails you want Copilot to use
• Name files in your prompt: Explicitly reference which files to use (e.g., "Using the attached Q3_budget.xlsx...")
• Be specific: Vague prompts produce generic outputs. Use the Goal → Context → Expectations → Source formula
• Check permissions: Ensure you have access to the files you're referencing

See Mindset → Prompting formula for more guidance.

A: Large language models can make errors with numbers, especially in complex calculations. This is why verification is essential:

• Always verify numbers: Check all calculations, dates, and amounts against source files
• Ask Copilot to show its work: Use prompts like "Show the formulas you used" or "List the cell references you read from"
• For critical calculations: Verify manually or use Excel formulas directly
• Attach source files: Ensure Copilot is working from your actual data, not guessing

See Trust & Safety for more on numerical errors and verification.

A: Specify tone and style explicitly in your prompt:

• State the audience: "for residents," "for council," "for colleagues"
• Specify tone: "friendly," "professional," "formal," "conversational"
• Provide examples: "Match the tone of [example document]" or attach a style guide
• Be specific: "Use plain language suitable for residents" is better than "make it friendly"

Remember: Always review outputs and adjust tone as needed. See Workflow Ideas for tone-specific examples.

A: Yes! Copilot works best when you iterate. You can:

• Ask for revisions: "Shorten this to 150 words" or "Make it more formal"
• Request additions: "Add a section on budget implications"
• Change format: "Convert this to a table" or "Create bullet points"
• Refine tone: "Make this more friendly" or "Adjust for council audience"

Treat Copilot like a conversation—each follow-up prompt builds on the previous output. See Mindset for more on iterative refinement.

A: Yes, when using Microsoft 365 Copilot within your organization. Copilot operates entirely within your Microsoft 365 tenant, meaning:

• Your data never leaves your organization's Microsoft 365 environment
• Copilot respects all existing security policies, permissions, and data loss prevention rules
• Your organization's data is not used to train Copilot's underlying model
• All interactions are subject to the same security controls as other Microsoft 365 activities

This is why organizations choose integrated AI solutions like Copilot—they provide security and compliance controls that standalone AI services cannot match. See Trust & Safety for more details.

A: This depends on your organization's policies. Generally:

• Check your policy: Review your organization's guidelines on using AI with sensitive data
• Respect data classification: Follow your data classification and handling policies
• Use judgment: If you wouldn't share information with an external service, be cautious with Copilot
• Verify outputs: Always review outputs before sharing to ensure no sensitive information leaked through

When in doubt, consult your IT or security team. See Trust & Safety for guidance on data leakage prevention.

A: Microsoft 365 Copilot processes your prompts and generates responses, but your organization's data and prompts are not used to train the underlying AI model. Interactions may be logged for security and compliance purposes, similar to other Microsoft 365 activities. Check with your IT department about your organization's specific logging and retention policies.

A: Always verify outputs before using them. Copilot is a drafting assistant, not a replacement for your judgment. Follow these steps:

1. Attach source files to ground Copilot's responses
2. Use clear, specific prompts with the Goal → Context → Expectations → Source formula
3. Review and verify all outputs—check facts, numbers, dates, and tone
4. Edit as needed to match your requirements and organizational standards

See Mindset → QA checklist for a complete verification guide.

A: Better prompts lead to better results. Follow these principles:

• Be specific: "Draft a two-paragraph resident notice" is better than "write something"
• Provide context: Include audience, purpose, and constraints
• Attach sources: Always attach the files you want Copilot to use
• Specify format: Tell Copilot what structure you want (table, bullets, paragraphs)
• Iterate: Refine outputs through follow-up prompts
• Practice: Start with simple tasks and build complexity gradually

See Workflow Ideas for proven prompt examples.