Skip to main content
Ruddr is available as one app in Microsoft Marketplace. It provides three things: the Ruddr app for Microsoft Teams, the Outlook calendar integration, and the Microsoft 365 Copilot connector. Nothing in this article gives anyone access to Ruddr data; members connect or link their own accounts afterwards. Microsoft Teams and the Outlook calendar need your Microsoft 365 organization connected to your Ruddr workspace. There are two ways to connect, and they end in the same place:
  1. Install from Ruddr: a Workspace Admin signs in with their Microsoft work account. This is the usual way.
  2. Install from Microsoft Marketplace: a Microsoft 365 administrator deploys Ruddr to the organization first, then a Workspace Admin connects.
Copilot works without the connection; each member connects from Copilot, as described in the Copilot article.

​
Install from Ruddr

  1. Navigate to the Integrations area under Settings and click Install on the Microsoft 365 widget (Figure 1).
  2. Sign in with your Microsoft work account. Choose an account that belongs to the organization you want to connect; personal Microsoft accounts and guest accounts are refused. The first time, Microsoft asks you to accept Ruddr’s sign-in permissions (your name, email and organization).
  3. Ruddr returns you to the Integrations area, where Microsoft 365 now appears in Active Integrations (Figure 2).

Figure 1 - The Microsoft 365 Widget in Available Integrations

Figure 2 - The Microsoft 365 Integration in Active Integrations

Only a Ruddr Workspace Admin can connect an organization. You don’t need to be a Microsoft 365 administrator for this step.
If Microsoft shows Approval required when you sign in, your organization restricts which apps users can consent to. Ask a Microsoft 365 administrator to grant consent for the organization, as described under Optional Steps for Microsoft 365 Administrators, and try again.
Members can now add the Ruddr app in Microsoft Teams from Apps and connect their Outlook calendar from My Profile. Ruddr is also listed as a data source in Copilot for anyone it is available to.

​
Install from Microsoft Marketplace

A Microsoft 365 administrator can deploy Ruddr to the organization first, so Ruddr is pre-installed in Teams and Copilot for the people they choose:
  1. Sign in to Microsoft 365 as an administrator, open the Ruddr listing in Microsoft Marketplace, and select Get it now (Figure 3).
  2. Confirm your details and select Get it now in the dialog (Figure 4). Marketplace takes you to the Microsoft 365 admin center, where the Deploy New App panel opens with Ruddr in it.
  3. Select Next, then choose who gets Ruddr under Assign users: Just me, All users, or Specific users or groups (Figure 5).
  4. Select Next, review the settings, and select Finish deployment. The panel reports Deployment completed (Figure 6).

Figure 3 - Get Ruddr from Microsoft Marketplace

Figure 4 - Confirm Your Details to Continue

Figure 5 - Choose Who Gets Ruddr

Figure 6 - The Ruddr Deployment Completed

A Workspace Admin then connects the organization to the workspace, either with Install in Ruddr as above, or from Microsoft Teams: send the Ruddr app a message, click Connect Ruddr to your organization on the Welcome to Ruddr card (Figure 7), choose the workspace and click Connect (Figure 8). The link works once and expires after 15 minutes. Connecting from Teams also links your own Microsoft Teams account.

Figure 7 - The Connect Ruddr to your organization Card in Microsoft Teams

Figure 8 - Connect your Microsoft 365 Organization to a Ruddr Workspace

A workspace can be connected to one Microsoft 365 organization. If the workspace is already connected to a different organization, Ruddr refuses the connection until a Workspace Admin removes the existing one (see Removing the Integration).

​
Optional Steps for Microsoft 365 Administrators

Once connected, click Settings on the Microsoft 365 widget to open the Microsoft 365 settings page. The page lists one row per area, each with a status and details: Organization (your organization’s domain, who connected it and when), Deployment, Consent, Microsoft Single Sign-On, Teams Members, Teams Projects, Teams Notifications, Outlook Calendar, and Copilot (Figure 9). Two rows hold optional actions that need a Microsoft 365 administrator:
  • Deployment: the external-link icon opens the Ruddr listing in Microsoft Marketplace in a new tab, for the deployment described above. Without it, members add Ruddr from the Teams app store themselves. It is required only in organizations that block third-party apps in Teams.
  • Consent: the shield icon sends the administrator to Microsoft to approve Ruddr’s permissions once for everyone: sign-in, and read-only access to each member’s own calendar. After that, members don’t see a consent prompt when they connect their calendar, and the row shows the date consent was granted in place of the action.

Figure 9 - The Microsoft 365 Settings Page

The Microsoft Single Sign-On row is described in Microsoft Single Sign-On below, and the Teams rows in the Microsoft Teams Integration Setup article.

​
Microsoft Single Sign-On

Microsoft Single Sign-On lets members sign in to Ruddr with their Microsoft account from the connected organization. It runs on the Microsoft 365 connection alone, with nothing to set up in Microsoft Entra. Once enabled, it appears under Settings > Authentication as the Microsoft 365 provider. It is separate from the Microsoft Entra ID provider, which uses SAML and is set up as described in Identity Provider Setup. To turn it on:
  1. On the Microsoft 365 settings page, click the edit icon on the Microsoft Single Sign-On row (Figure 10).
  2. Select Enable Microsoft Single Sign-On (Figure 11).
  3. Optionally, select Make it the default sign-in method to make it the workspace’s default authentication provider.
  4. Optionally, select Create members on first sign-in so that someone from your organization who isn’t a member yet gets a Ruddr account the first time they sign in. Then choose the Security Role for new members, which is required. You can also choose a Member Template for the rest of the new member’s settings; picking a template fills in its security role, which you can change. New members created this way use Microsoft Single Sign-On as their sign-in method.
  5. Click Save & Close. The row now shows a check mark and the options you chose.

Figure 10 - Microsoft Single Sign-On Enabled on the Microsoft 365 Settings Page

Figure 11 - The Microsoft Single Sign-On Drawer

A template marked with a warning icon in the list has settings that first sign-in can’t use. Hover over the icon to see each one:
  • Manager approvals - Members created on first sign-in don’t have a manager. If the template sets time off or expense approvals to Manager, these members get the default approval mode until a manager is assigned. Set their approvals after you assign a manager.
  • Authentication provider - If the template sets a different authentication provider, new members use Microsoft Single Sign-On instead.
The Sign-in Link
Once Microsoft Single Sign-On is enabled, the drawer shows your workspace’s sign-in link, in the form https://www.ruddr.io/login/microsoft/<workspace key>, with a button to copy it (Figure 11). Share it with your members. The link opens a page with your workspace’s name and logo, where a member clicks Sign in with Microsoft (Figure 12). A member who is already signed in goes straight into the workspace.

Figure 12 - Sign in to the Workspace with Microsoft

Members can also use the regular login page: after they enter their email, members of a workspace with Microsoft Single Sign-On enabled see a Sign in with Microsoft button.
How Members Are Matched
Ruddr matches the Microsoft account to a member in this order:
  1. The Microsoft account the member already linked through Microsoft Teams or the Outlook calendar.
  2. The member’s email address.
When the match is by email, Ruddr links the Microsoft account to the member, and the member’s history records Linked to Microsoft account with the account name. A member created on first sign-in has Created by Microsoft Single Sign-On in their history. A member with a pending invitation who signs in successfully accepts the invitation. Only accounts from the connected organization can sign in. Guest accounts and accounts from other Microsoft 365 organizations are refused.
Turning It Off
To turn Microsoft Single Sign-On off, open the drawer, clear Enable Microsoft Single Sign-On, and click Save & Close. If it was the default sign-in method, the password method becomes the default again. Members keep their Ruddr accounts. Removing the integration turns Microsoft Single Sign-On off too.

​
What Each Offering Needs

​
Removing the Integration

To disconnect your organization, click the Remove button on the Microsoft 365 widget (Figure 2) and confirm (Figure 13). Removing the integration disconnects your Microsoft 365 organization and removes the Microsoft Teams settings, project channels, every member’s Microsoft Teams link, and every member’s calendar connection. It also turns off Microsoft Single Sign-On. Time entries are not affected. Members aren’t notified; the organization can be connected again at any time. Copilot connections are separate and are not affected.

Figure 13 - Remove the Microsoft 365 Integration