Skip to main content
Connecting Edurie to your school’s Microsoft 365 tenant brings your official class data into the Microsoft tools your staff and students use every day. Once connected, Edurie keeps Microsoft Teams channels, Outlook calendar events, and OneDrive folders in sync with your rosters and schedules — automatically. Changes made in Edurie, such as enrolling a student or updating a class schedule, are pushed to Microsoft 365 without any manual work on your part.

​
Prerequisites

Before connecting Microsoft 365, confirm the following:
  • Your school has an active Microsoft 365 Education subscription (A1, A3, or A5).
  • You are a Microsoft 365 Global Administrator or have been delegated sufficient admin consent rights in your Azure Active Directory tenant.
  • You know your school’s Azure AD Tenant ID. You can find this in the Azure portal under Azure Active Directory → Overview.
Connecting Microsoft 365 requires an admin to grant tenant-wide consent to the Edurie application in Azure AD. This is a one-time step that allows Edurie to manage Teams, calendars, and directory objects on behalf of your school. Without admin consent, the OAuth flow will complete but sync operations will fail with permission errors.

​
Available services

Microsoft Teams

Creates a Teams channel for each class offering. Syncs student and teacher rosters automatically, keeping membership current as enrolments change.

Microsoft Outlook

Creates Outlook calendar events for scheduled class sessions and updates them automatically when the schedule changes.

Microsoft OneDrive

Provisions a shared OneDrive folder for each class so teachers can distribute and organize course materials within the familiar Microsoft ecosystem.

​
Connecting Microsoft 365

1

Open Apps & Integrations

In your Edurie admin panel, select your school and navigate to Apps & Integrations in the left sidebar.
2

Select Microsoft 365

Find the Microsoft 365 tile and click Connect. The setup dialog opens.
3

Enter your Azure AD Tenant ID

Type or paste your school’s Azure AD Tenant ID into the provided field. Edurie uses this to route the OAuth request to the correct Microsoft identity platform endpoint.
4

Authorize with your admin account

Click Authorize with Microsoft. You are redirected to Microsoft’s identity platform. Sign in with your Microsoft 365 Global Administrator account.
On the Microsoft consent screen, you must check Consent on behalf of your organization before clicking Accept. If you skip this step, Edurie will connect to your personal account only — sync operations that require application-level permissions (such as creating Teams channels or reading directory data) will fail.
5

Enable services

After authorization returns you to Edurie, toggle on the Microsoft services you want to activate: Teams, Outlook, and/or OneDrive. You can adjust these selections at any time from the integration settings.
6

Save and verify

Click Save. Edurie verifies the connection and sets the integration status to Connected. The initial sync for all existing classes runs automatically in the background.

​
How sync works

​
Automatic sync triggers

Edurie triggers a Microsoft 365 sync automatically when relevant data changes. Common triggers include:
EventServices synced
Student enrolled in a classTeams channel membership, Outlook calendar events
Student removed from a classTeams channel membership
Class schedule updatedOutlook calendar events
Class name or section changedTeams channel name, calendar event titles
New class created with integrations enabledAll enabled services for that class

​
Manual sync

To manually trigger a sync for a specific class, open the class in Edurie, go to the Integrations tab, and click Sync next to the service you want to re-sync. Edurie queues the job and processes it within seconds for most classes.

​
Managing sync logs

Every sync operation is logged. To review logs for your Microsoft 365 integration:
  1. Go to Apps & Integrations → Microsoft 365 → Sync Logs.
  2. Filter by status (pending, success, failed, skipped) or search by class name.
  3. Click any entry to see the full details, including the error message returned by Microsoft if the operation failed.
To retry a failed operation without waiting for the next automatic trigger, click Retry on the log entry. Edurie re-queues it immediately.

​
Resolving sync conflicts

A conflict is created when data in Edurie and Microsoft 365 diverge in a way Edurie cannot automatically reconcile — for example, if a user’s display name is edited directly in Azure AD after being synced from Edurie. To review and resolve conflicts:
  1. Go to Apps & Integrations → Microsoft 365 → Conflicts.
  2. Open each pending conflict and compare the Edurie version with the Microsoft 365 version.
  3. Choose how to resolve it:
    • Accept external — Update Edurie to match Microsoft 365.
    • Push local — Overwrite Microsoft 365 with Edurie’s data.
    • Ignore — Dismiss the conflict without changing either system.
Ignoring a conflict does not fix the underlying data mismatch. If the same field is synced again, a new conflict may be created. Resolve conflicts by choosing a definitive source of truth for each field.

​
Frequently asked questions

You need Microsoft 365 Education A1 or higher. Teams, Outlook, and OneDrive for Education are all included with the free A1 plan. Higher tiers (A3, A5) unlock additional security and compliance features but are not required for the core Edurie integration.
When a class is deleted in Edurie, Edurie archives the associated Teams channel to preserve any posted messages and files. Archived channels remain accessible to teachers in read-only mode but no longer appear as active channels for students.
Each school in Edurie supports one Microsoft 365 integration tied to one Azure AD tenant. If your institution has multiple schools in Edurie, each school can connect its own Microsoft 365 tenant independently.
A sync is marked as skipped when Edurie determines that no changes need to be pushed — for example, if the class data in Edurie already matches what is in Microsoft 365. Skipped entries are normal and do not indicate an error. If you believe a sync should have run but was skipped, check whether the relevant service toggle is enabled for that class and confirm that the integration status is Connected.