Microsoft OAuth Credentials

Connect a Microsoft account to Jinba Flow with OAuth for Outlook and other Microsoft tools.

Configure Microsoft OAuth to access Microsoft services such as Outlook Calendar from your Jinba Flow workflows.

Prerequisites

• A Microsoft account

Setting Up in Jinba Flow

1. Go to your workspace settings in Jinba Flow
2. Navigate to the “Secret” section
3. Find the Microsoft OAuth credential in the list of available credentials
4. Click “Configure” or “Add New”
5. Follow the authentication flow:
   • Sign in with your Microsoft account
   • Review and accept the requested permissions
   • You’ll be redirected back to Jinba Flow
   • Your OAuth tokens will be securely stored

OAuth Flow

When you first use Microsoft-connected tools in your flows:

1. Jinba Flow redirects you to Microsoft’s OAuth consent screen
2. Sign in with your Microsoft account
3. Review and accept the requested permissions
4. You’ll be redirected back to Jinba Flow
5. Your OAuth tokens will be securely stored

Available Microsoft Services

Outlook Calendar

• Create events
• Find events
• Update events
• Delete events

Outlook Mail

• List messages and send messages (OUTLOOK_LIST_MESSAGES, OUTLOOK_SEND_MESSAGE), with a secret of type MICROSOFT_GRAPH_OUTLOOK

SharePoint

• List sites and documents, search, download and upload files (SHAREPOINT_* tools), with a secret of type MICROSOFT_GRAPH_SHAREPOINT

Teams

• List teams, channels, chats and messages, send and reply to messages, and read online meetings (TEAMS_* tools), with a secret of type MICROSOFT_GRAPH_TEAMS

User Directory

• Look up users and their managers (MICROSOFT_GET_USERS, MICROSOFT_GET_MANAGER), with a secret of type MICROSOFT_GRAPH_USERS

Each connector has its own secret type, so connect each one you use separately. Outlook Calendar uses MICROSOFT_GRAPH_OUTLOOK_CALENDAR.

Organization Admin Consent

Some Microsoft 365 tenants do not let users consent to applications themselves. In that case the Microsoft sign-in stops at Need admin approval, and a tenant administrator has to grant consent once for the whole organization.

Jinba Flow generates that consent link for you, scoped to the connector you are setting up (Outlook Mail, Outlook Calendar, SharePoint, Teams or User Directory). Administrators can therefore approve exactly the connectors your organization wants to use, and nothing more. Granting consent in the Entra admin center through the application’s Grant admin consent button is not required and does not cover these permissions.

1. In the Jinba secrets dashboard, choose the Microsoft connector you want to connect.
2. Under Organization admin consent, click Copy admin consent link and send the link to a tenant administrator. The link stays valid for 7 days. If you are an administrator yourself, click Open as admin instead.
3. The administrator opens the link, signs in and accepts the permissions on behalf of the organization.
4. Everyone in the tenant can now connect that connector from the secrets dashboard without further approval.

All Microsoft connectors generates one link that covers every Microsoft connector at once, for organizations that prefer a single approval.

If a user is blocked before consent has been granted, Jinba Flow shows “Your organization requires admin approval” together with the consent link for that connector, so the user can forward it to their administrator directly. Consent has to be granted again only when Jinba Flow adds new permissions to a connector or when the organization uses a connector for the first time.

Secret Usage in Flows

Outlook Calendar examples use the following secret reference:

config:
  - name: token
    value: "{{secrets.MICROSOFT_GRAPH_OUTLOOK_CALENDAR}}"

Related Pages

• Outlook Calendar
• Productivity Tools

Troubleshooting

• If authentication fails, reconnect the credential from the Jinba secrets dashboard
• If your organization restricts Microsoft app consent, send your administrator the link described in Organization Admin Consent
• If a flow reports an invalid or expired token, re-authenticate the credential and run the flow again