Connect Microsoft Outlook to Amazon Quick Suite
Learn how to connect Microsoft Outlook to Amazon Quick Suite to manage emails, calendar events, and contacts using natural language.
Your inbox fills up throughout the day. When you need to send an email, check your calendar, or find a contact, you open Outlook, complete the task, and switch back to what you were doing. These constant context switches between applications break your focus and slow you down.
Amazon Quick Suite can help reduce this friction. Quick Suite is an AI-powered workspace that answers your questions and turns those answers into actions. The workspace includes Amazon Quick Sight for data visualization, Amazon Quick Flows for building automations with natural language, Amazon Quick Automate for enterprise-scale process automation, Amazon Quick Index for connecting and searching organizational data, and Amazon Quick Research for in-depth analysis across documents and datasets. With the Microsoft Outlook integration, you can manage emails, calendar events, and contacts directly from Quick Suite.
This guide walks through setting up the Microsoft Outlook action integration with user authentication. User authentication means each person signs in with their own Microsoft account, and actions run with their permissions. If you send an email, it's sent as you. If you create a calendar event, it appears on your calendar.
Prerequisites
Before you begin, make sure you have the following:
- Amazon Quick Suite Enterprise subscription or higher
- Microsoft 365 account with Outlook or Exchange Online access
- Access to the Microsoft Entra admin center with at least Application Developer permissions
- Permission to create app registrations in your Microsoft Entra tenant
How user authentication works
When you set up user authentication (also called three-legged OAuth or 3LO), you create an app registration in Microsoft Entra. This app registration establishes a trust relationship between Quick Suite and Microsoft's identity platform.
The trust relationship enables each user to sign in with their Microsoft account the first time they use the integration. Quick Suite stores their authorization and uses it for subsequent requests. All actions run with the signed-in user's permissions, so if a user can't access a mailbox directly, they can't access it through Quick Suite either.
This permission model provides security through the principle of least privilege. Quick Suite can only do what the authenticated user can do, which means your organization's existing access controls remain in effect.
Configure Microsoft Entra
Before configuring Quick Suite, you need to create an app registration in Microsoft Entra. This app provides the credentials Quick Suite uses to authenticate users.
To create the app registration:
- Open the Microsoft Entra admin center .
- In the left navigation, choose Entra ID, then choose App registrations.
- Choose New registration.
- For Name, enter
Quick Suite Outlook Action Integration - User Auth. - For Supported account types, choose Accounts in this organizational directory only. This restricts the app to users in your tenant.
- For Redirect URI, select Web from the dropdown, then enter
https://{region}.quicksight.aws.amazon.com/sn/oauthcallback. Replace{region}with the AWS Region where your Quick Suite instance is deployed (for example,us-east-1). - Choose Register.
After registration completes, keep this page open. You need the Application (client) ID and Directory (tenant) ID values for the Quick Suite configuration.
Quick Suite needs a client secret to authenticate with Microsoft Entra. This secret acts as a password for the app registration.
To create a client secret:
- From your app registration, choose Certificates & secrets in the left navigation.
- Choose the Client secrets tab.
- Choose New client secret.
- For Description, enter
Quick Suite Outlook Action Integration - User Auth Secret. - For Expires, choose an expiration period. Consider your organization's security policies when selecting this value.
- Choose Add.
- Copy the Value immediately. This value is only shown once. If you navigate away without copying it, you must create a new secret.
Important: Copy the secret Value, not the Secret ID. The Value is the longer string that starts with characters likeabc8Q~....
The app registration also needs permissions to access Outlook through Microsoft Graph. These permissions determine what actions Quick Suite can perform on behalf of users.
To configure API permissions:
- From your app registration, choose API permissions in the left navigation.
- The User.Read permission for Microsoft Graph is already added by default. Leave this permission in place.
- Choose Add a permission.
- Choose Microsoft Graph.
- Choose Delegated permissions.
- Search for and select the following permissions:
Mail.ReadWrite- Read and write access to user mailMail.Send- Send mail as a userCalendars.ReadWrite- Read and write access to user calendarsCalendars.ReadWrite.Shared- Read and write user and shared calendarsUser.Read.All- Read all users' basic profilesContacts.Read- Read user contactsPlace.Read.All- Read all place information (for meeting room availability)MailboxSettings.Read- Read user mailbox settingsoffline_access- Allows the app to retrieve a refresh token
- Choose Add permissions.
Your API permissions list now includes these entries:
| API | Permission | Type | Description |
|---|---|---|---|
| Microsoft Graph | User.Read | Delegated | Sign in and read user profile |
| Microsoft Graph | Mail.ReadWrite | Delegated | Read and write access to user mail |
| Microsoft Graph | Mail.Send | Delegated | Send mail as a user |
| Microsoft Graph | Calendars.ReadWrite | Delegated | Read and write access to user calendars |
| Microsoft Graph | Calendars.ReadWrite.Shared | Delegated | Read and write user and shared calendars |
| Microsoft Graph | User.Read.All | Delegated | Read all users' basic profiles |
| Microsoft Graph | Contacts.Read | Delegated | Read user contacts |
| Microsoft Graph | Place.Read.All | Delegated | Read all place information |
| Microsoft Graph | MailboxSettings.Read | Delegated | Read user mailbox settings |
| Microsoft Graph | offline_access | Delegated | Maintain access to data you have given it access to |
Some permissions in the list above require administrator consent before users can authenticate. The
User.Read.All and Place.Read.All permissions fall into this category. If your organization requires admin consent for these permissions, an administrator must grant consent before users can use the integration.To grant admin consent:
- From the API permissions page, choose Grant admin consent for [your tenant name].
- Choose Yes to confirm.
After consent is granted, the Status column shows Granted for [your tenant name] for all permissions.
Before leaving the Microsoft Entra admin center, record the following values. You need them for the Quick Suite configuration.
| Value | Where to find it |
|---|---|
| Application (client) ID | App registration Overview page |
| Directory (tenant) ID | App registration Overview page |
| Client secret value | Certificates & secrets page (copied earlier) |
Configure Amazon Quick Suite
Now that you have the app registration configured, you can create the Microsoft Outlook action integration in Quick Suite. This integration uses the credentials from Microsoft Entra to authenticate users.
To create the action integration:
- Open Quick Suite (for example,
https://us-east-1.quicksight.aws.amazon.com/). - In the navigation pane, choose Integrations, then choose Actions.
- Find Microsoft Outlook and choose the Add (+) button.
- On the Create integration page, configure the following:
- For Name, enter
Microsoft Outlook Integration - User Auth. Adding "User Auth" helps distinguish this from service authentication integrations. - For Description, enter a description such as
Manage emails, calendar events, and contacts. See available actions for details. - For Connection type, choose public.
- For Name, enter
- Under Authentication settings, configure the authentication method:
- For Authentication method, choose User authentication.
- For Authentication type, choose Custom user based OAuth.
- Configure the OAuth connection settings using the values from the table below.
- Choose Create and continue.
- (Optional) Choose users or groups to share the integration with. You can assign them as owners or viewers.
- Choose Create.
Use the following values for the OAuth connection settings. Replace
{your-tenant-id} with your Directory (tenant) ID from Microsoft Entra. The Redirect URL is pre-filled based on your region.| Field | Value |
|---|---|
| Base URL | https://graph.microsoft.com/v1.0 |
| Client ID | Your Application (client) ID from Microsoft Entra |
| Client secret | Your client secret value |
| Token URL | https://login.microsoftonline.com/{your-tenant-id}/oauth2/v2.0/token |
| Authorization URL | https://login.microsoftonline.com/{your-tenant-id}/oauth2/v2.0/authorize |
| Redirect URL | https://{region}.quicksight.aws.amazon.com/sn/oauthcallback (pre-filled) |
After creating the integration, you need to sign in with your Microsoft account to authorize it.
To authenticate the integration:
- In Quick Suite, choose Integrations, then choose Actions.
- Find your Outlook integration and choose Sign in.
- A Microsoft sign-in window opens. Enter your Microsoft account credentials.
- Review the permissions the app is requesting.
- (Optional) If you're an administrator and want to consent on behalf of your entire organization, select Consent on behalf of your organization.
- Choose Accept to grant the requested permissions.
After authentication completes, the integration status changes to show you're signed in.
Test the connection
To verify the integration is working, try a read action first.
To test the integration:
- In Quick Suite, choose the chat icon in the top right navigation.
- In the chat footer, choose All data and apps.
- Ask the agent: "List my recent emails."
- Verify that Quick Suite returns emails from your mailbox.
If the test succeeds, try sending an email: "Send an email to myself with the subject 'Test from Quick Suite' and body 'This is a test message.'"
Available actions
After setting up the Microsoft Outlook integration, you can perform operations on emails, calendar events, contacts, and mailbox settings. The following table lists the available actions:
| Category | Action | Description |
|---|---|---|
| List User Mails | View emails in your mailbox | |
| List Folder Message | View messages in a specific mail folder | |
| View Email | Get email details by ID | |
| Send User Email | Send a new email message | |
| Reply To Email | Reply to an existing email | |
| Forward User Email | Forward an email to other recipients | |
| Update Email | Edit email properties | |
| Delete Email | Remove an email from your mailbox | |
| Move Email To Folder | Move an email to a different folder | |
| List Email Attachment | View attachments on an email | |
| Get Attachment | Get attachment details and content by ID | |
| Calendar | List Calendar Events | View events on your calendar |
| Calendar | List Calendar View | View meetings in a specified date range |
| Calendar | Create Calendar Event | Create a new meeting or appointment |
| Calendar | Update Calendar Event | Modify an existing event |
| Calendar | Delete Calendar Event | Remove an event from your calendar |
| Calendar | Find Meeting Times | Suggest meeting times based on attendee availability |
| Contacts | List Contacts | View your contacts |
| Users | List Users | View users in your organization |
| Settings | Get Mailbox Settings | Read mailbox configuration |
| Places | List Places | View meeting rooms and room lists |
Tips for prompting
The Outlook connector works through conversation. You don't need to know the technical details of the API. Instead, ask the agent what it can do and let it guide you.
Start by asking what's possible. If you're unsure what the Outlook connector can do, ask the agent directly. For example, "What can you do with Outlook?" or "What Outlook actions are available?" The agent describes the available capabilities, helping you understand what's possible before you make a request.
Ask follow-up questions when results are incomplete. When you ask to see your emails, the agent returns a limited set of results. If you need more, ask for them. For example, after seeing your recent emails, you might say "Show me more emails" or "Show me the next 10 emails." The agent handles the details of retrieving additional results.
Use search when looking for specific emails. Rather than scrolling through results, ask the agent to search. For example, "Search my emails for messages about the quarterly report" or "Find emails from
john_stiles@example.com." The agent uses the search capability to find matching messages.Be specific about recipients when sending emails. Include the full email address rather than just a name. For example, "Send an email to
john_stiles@example.com with the subject 'Project Update'" works better than "Send an email to John about the project."Provide explicit dates and times for calendar events. When creating meetings, include the specific date, time, and duration. For example, "Create a 30-minute meeting on February 10, 2026 at 2:00 PM with
saanvi_sarkar@example.com to discuss the project update." This specificity helps the agent create the event correctly.Provide date ranges when viewing calendar events. To see your schedule, specify the time period. For example, "Show my calendar events from February 10 to February 14, 2026" or "What meetings do I have next week?" The agent retrieves events within that range.
Use folder names for email operations beyond your inbox. To work with specific mail folders, include the folder name in your request. For example, "Show emails in my Sent Items folder" or "Move this email to my Archive folder." If you're unsure what folders exist, ask "What mail folders do I have?"
Use cases
With the Microsoft Outlook integration configured, your team can manage email and calendar without leaving Quick Suite.
Scheduling meetings becomes a conversation rather than a context switch. Create calendar events directly from chat by specifying the attendees, date, time, and subject. For example, "Create a meeting on March 5, 2026 at 10:00 AM for 1 hour with
alejandro_rosalez@example.com and martha_rivera@example.com. Subject: Quarterly Review. Location: Conference Room A." The agent creates the event and sends invitations to the attendees.Finding available meeting times across multiple calendars no longer requires opening each person's calendar. Ask the agent to find times when attendees are free. For example, "Find meeting times when
saanvi_sarkar@example.com and mateo_jackson@example.com are both available for a 1-hour meeting between March 1 and March 7, 2026." The agent checks availability and suggests times that work for everyone.Forwarding emails to colleagues happens without leaving your current context. When you receive an email that someone else needs to see, forward it directly. For example, "Forward this email to
mary_major@example.com with the comment 'FYI - see the customer request below.'" The agent forwards the email with your comment included.Viewing and retrieving attachments works through the chat interface. When reviewing emails, you can list attachments and retrieve their content. For example, "List attachments on this email" shows what files are attached, and "Get the attachment named 'report.pdf'" retrieves the file content.
The Outlook integration becomes more powerful when combined with Amazon Quick Flows. Quick Flows lets you build multi-step workflows that chain actions across different systems. For example, you might receive contact form submissions in your inbox from prospects requesting a free trial. Rather than manually copying each request into a tracking spreadsheet, you can create a flow that reads emails from a specific folder, extracts the contact details, and writes them to a SharePoint list. You can then schedule this flow to run daily, so new requests are automatically captured without manual effort.
Another common pattern is the daily briefing flow. You can create a flow that runs each morning before work, retrieves your calendar events for the day, and sends you a summary email with your schedule and any preparation notes. The flow uses the List Calendar View action to get your events, processes them with AI to generate a briefing, and uses Send User Email to deliver the summary to your inbox.
You can also build flows that respond to completed work in Quick Suite. After a dashboard analysis reveals an important trend, a flow can draft an email with the key findings and send it to stakeholders. The flow gathers insights from Quick Sight, generates a summary using AI, and uses the Outlook action to send the notification. This pattern keeps stakeholders informed without requiring you to context-switch between applications.
Cleanup
To remove the resources created in this guide:
- In Quick Suite, choose Integrations, select your Outlook integration, and choose Delete.
- In the Microsoft Entra admin center, choose App registrations, select the Quick Suite app, and choose Delete.
Conclusion
In this guide, I explained how to connect Microsoft Outlook to Amazon Quick Suite with user authentication. You created an app registration in Microsoft Entra, configured API permissions for email, calendar, and contacts access, and set up the integration in Quick Suite. You can now send emails, create calendar events, find meeting times, and view contacts directly from chat agents and automated workflows.
For more information, see the Microsoft Outlook integration documentation .
Resources
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article