- Information Technology Solutions
- Artificial Intelligence
- Microsoft 365
- Mission, Vision & Values
- Partner Directory
- Academic Technology
- Duplicating Services
- news
- Software available to current Students, Faculty and Staff
- Internet Access Resources
- Processes & Policies
- Zoom Session Recording & Privacy Considerations
Coexistence Testing Scenario
Scenario | Steps | Expected Results |
Send email internally (M365 -> M365) include attachment | 1. User A (migrated) compose/sends email to User B (also migrated) | Email is delivered to User B's InBox. |
Send email across environments (M365 → G Suite user and vice versa) include attachment |
1. User A (migrated) sends to User C (still on G Suite).
2. User C in GSuite sends email to migrated user
|
1.Email is delivered to User C receives email in their InBox.
2.User C responds to User A
3.Successful receipt on both ends
|
Receive external email |
1. Send email from an external email account to User A.
2. Verify receipt.
|
User A receives email and responds |
Reply/Reply All |
1. User A replies to internal and cross-platform threads.
2. Reply and Reply-All.
|
Replies go to correct recipients; thread context preserved. |
Forward with attachments |
1. Forward received message with attachments to internal/external user.
2. Verify attachment integrity.
|
Attachments intact, able to open, |
Online archive access |
1. Place items into Online Archive.
2. Search and retrieve archived items.
|
Archived mails appear in Online Archive folder; searchable. |
Mobile client mail sync |
1. Configure Outlook mobile for User A.
2. Send/receive, folder sync, attachment download.
|
Mail syncs within tolerance (<1 min); attachments open. |
OWA vs Outlook desktop |
1. Perform 1–7 via Outlook Web App.
2. Verify feature parity (attachments, actionable messages).
|
All actions succeed identically in OWA. |
Mail flow rules |
1. Create Exchange transport rule (e.g., append disclaimer).
2. Send test mail.
|
rule matched correctly. |
Calendar
Scenario | Steps | Expected Results |
Create/modify meeting (M365 → M365) |
1. User A schedules meeting with User B.
2. Modify time/recurrence.
|
Invitations sent/updated; both see changes. |
Invite cross-platform (M365 → G Suite user) |
1. User A invites User C (G Suite) to meeting.
2. User C accepts from Google Calendar.
3. Verify attendance status in M365.
|
Acceptance reflected in attendee list; free/busy updated.
|
Free/busy availability across platforms |
1. Check calendar availability of M365 and G Suite users.
2. Attempt to schedule in a free slot.
|
Free/busy shows correctly (verify no conflicts). |
Meeting cancellation |
1. Cancel meeting.
2. Verify cancellation notices received by all attendees.
|
Notices received; events removed from calendars. |
Resource mailbox booking |
1. Create/approve resource (e.g., meeting room) in Exchange.
2. Book via Outlook and OWA.
|
Booking confirmed; double-booking prevented. |
Scenario | Steps | Expected Results |
G-Drive -> Onedrive | Access Onedrive ensure G-Drive data migrated correctly | OneDrive documents accessible and editable |
File upload & download |
1. Upload files via web, desktop (mobile??).
2. Download from another device.
|
Files sync bi-directionally; integrity maintained.
|
Co-authoring Office doc |
1. Open Word/Excel from OneDrive on two machines.
2. Simultaneously edit.
|
Changes merge in real-time; version history preserved. |
Version history & restore |
1. Modify a file several times.
2. Use Version History to revert.
|
Older versions accessible; restoration succeeds. |
File sharing/internal & external ( and To GSuite) |
1. Share file/folder with internal user and external (anonymous link).
2. Verify access levels.
|
Links work per settings; external requires link only; internal uses AAD auth |
Sync conflict resolution |
1. Create conflicting edits offline.
2. Sync.
|
Conflict copies created; user prompted to reconcile. |
Files on-demand behavior |
1. Enable Files On-Demand.
2. Access placeholder and online-only files.
|
Placeholder appears; file downloads on open; disk usage minimal. |
Mobile OneDrive functionality |
1. Perform 1–7 via Outlook Web App.
2. Verify feature parity (attachments, actionable messages).
|
All actions succeed identically in OWA. |
Mailbox storage limits |
1. Upload photo, open Office file, share link.
|
All actions succeed with same permissions. |