Below you'll find the technical and security details for the Outlook calendar integration.
Security
Privacy Statement: https://privacy.microsoft.com/en-gb/privacystatement
Terms of Use: https://www.microsoft.com/en-us/legal/terms-of-use
Data Security: https://www.microsoft.com/en-us/trust-center/privacy
Authentication Protocols
Scopes Requested:
offline_access, calendars.readwrite
OAuth 2.0
Imported Data
Calendar | Allocation |
Calendar ID | Calendar Events |
| Event Titles (optional) |
| Start Date |
| End Date |
| Hours (if available) |
| Notes |
| Start time |
| Repetition rules ( We convert from Outlook to Float format) |
Exported Data
Time Off | Allocation |
Event Subject (time off type name) | Event Subject (task name + project name + client name if available) |
Event Body (time off notes) | Event Body (task notes) |
Event Start Date (time off start date) | Even Start Date (task start day) |
Event End Date ( time off end date) | Event End Date (task end day) |
Event Start time (time off start time - if defined) | Event Start Time (task start time, if defined) |
Event recurrence (converted from Float repeated configuration) | Event recurrence (converted from Float repeated configuration) |
Troubleshooting admin consent when connecting Outlook
If your team uses Microsoft's default user consent settings, or another workflow requiring Microsoft admin approval for apps, a Microsoft admin will need to grant access consent on the Permissions tab for Float within Microsoft, which should include Calendars.ReadWrite and Offline_access. If a Microsoft admin is unable to grant admin consent for Float, please ask them to follow these steps:
Delete the Float app in Microsoft in Enterprise app > Manage > Properties.
2. Grant access to Float with the link below (replacing tenant_id with the tenant ID you see in Entra):
4. Once access has been granted, please check if a team member can connect their calendar from Float.
