-
-
Power BI Introduction;
-
Improvements to the ROSI Power BI Class List reports in 2026;
-
ROSI Downloads and ROSI Download Header Files;
-
Excel Text Import Wizard tutorial;
-
How to differentiate and convert between file types used in ROSI (e.g., *.TXT vs. *.PRN vs *.CSV).
-
Microsoft Teams Live Events will be retiring on June 30, 2026
This is a notice that Microsoft Teams Live Events will be retiring on June 30, 2026. Microsoft has already started restricting scheduling so that Teams Live Events cannot be created for dates after June 30, 2026.
What is changing
- Microsoft Teams Live Events (and the Microsoft Graph Application Programming Interfaces (APIs) used to create them) will be fully discontinued on June 30, 2026.
- Teams Live Events already scheduled before June 30, 2026 will continue to run through February 28, 2027.
- Microsoft recommends moving to Teams town hall for events at scale.
Who is affected
- Anyone who schedules, produces or attends Teams Live Events.
Recommended actions
- Effective immediately, schedule new large-audience broadcasts as a Teams town hall (not a Teams Live Event), especially for any event after June 30, 2026.
- Review any upcoming communications plans that still reference “Teams Live Events” and update them to “Teams town hall.”
AMS FI Fiscal Year-End Closure 2026
To: AMS Users
From: Enterprise Applications & Solutions Integration
Re: AMS FI Fiscal Year-End Closure 2026
Hi everyone,
In collaboration with Financial Services, this year AMS will close for FI year-end processing on Tuesday, April 28 at 7 p.m. and will re-open on Friday, May 1 at 7 a.m.
Please note:
- uSOURCE will close on Tuesday, April 28 at 5 p.m. and will re-open on Friday, May 1 at 9 a.m.
- The Capital Projects Portal and Invoice Workflow will resume regular functionality on Friday, May 1 at 7 a.m.
- Concur (Travel & Expense Reimbursement) will remain available 24/7; however, posting claims or progressing the workflow after an approval is dependent on AMS and will automatically resume when AMS is available on May 1 at 7 a.m.
- Fiori Launchpad will remain available.
For information on the year-end deadlines, processing and reporting refer to the Financial Services website.
The following summarizes the AMS system availability during the weeks prior to year-end closing:
| Date | Status |
| Tuesday, April 14 | System closes for bi-weekly payroll at 5 p.m. |
| Wednesday, April 15 | System re-opens at 7 a.m. |
| Thursday, April 16 | System open regular hours |
| Friday, April 17 | System open regular hours |
| Saturday, April 18 | System open regular hours |
| Sunday, April 19 | System open regular hours |
| Monday, April 20 | System open regular hours |
| Tuesday, April 21 | System closes for “Copy Plan to Budget” at 7 p.m. |
| Wednesday, April 22 | System re-opens at 7 a.m. System closes for monthly payroll phase 1 at 5 p.m. |
| Thursday, April 23 | System re-opens at 7 a.m. System closes for monthly payroll phase 2 at 5 p.m. |
| Friday, April 24 | System re-opens at 7 a.m. |
| Saturday, April 25 | System open regular hours |
| Sunday, April 26 | System open regular hours |
| Monday, April 27 | System open regular hours |
| Tuesday, April 28 | System closed to all users at 7 p.m. except uSOURCE closes at 5 p.m. |
| Wednesday, April 29 and Thursday, April 30 | System closed to all users |
| Friday, May 1 | System re-opens at 7 a.m. except uSOURCE opens at 9am |
Please visit our System Availability page for information on all systems.
Sincerely,
Enterprise Applications & Solutions Integration (EASI)
Outlook on the web change: personal accounts + combined calendar view retiring (March – June 2026)
To: AMS Listserv
From: Enterprise Applications & Solutions Integration
Re: Outlook on the web change: personal accounts + combined calendar view retiring (March – June 2026)
Dear colleagues,
Microsoft is retiring two Outlook on the web (OWA) features between early March and late June 2026:
- OneView (connecting personal email like Gmail/Outlook.com/IMAP into OWA)
- TrueTime (viewing personal + work calendars together in OWA)
If you don’t use personal accounts or personal calendars inside OWA, no action is required.
If you do use these features:
- Your connected personal account(s) in OWA will be automatically disconnected as Microsoft rolls this out.
- For multi-account workflows, use Outlook for Windows/Mac, or keep personal accounts separate (e.g., a separate browser profile/window).
If you have any further questions or concerns, please submit a ticket to the Enterprise Service Centre at (https://uoft.me/m365help).
Sincerely,
Enterprise Applications & Solutions Integration (EASI)
ROSI Database Quarterly Maintenance – Friday, March 27
To: ROSI Users; Registrar’s Offices
From: Enterprise Applications & Solutions Integration
Re: ROSI Database Quarterly Maintenance – Friday, March 27
Dear ROSI users,
Please note that we will need to take ROSI and most associated student information systems offline on Friday, March 27 from 5 to 9 p.m. to perform quarterly maintenance on the database. We will return the systems to service sooner if the work is completed earlier than 9 p.m.
The ROSI-REPLICA on the Managed Instance (MI) will remain accessible during the maintenance. Data syncing with the ROSI transactional database will restart 10 – 20 minutes after the end of the maintenance period and applications have been restarted.
The following systems will be affected:
- Accommodated Testing Services (Student and Admin)
- ACORN
- Course Information System
- Degree Explorer (Student and Admin)
- EASI Institutional File Transfer
- eMarks
- Online Administrative Student Information System (OASIS) – including Absence Declaration, and the Timetable Builder and Transfer Equivalencies database administrative screens
- ROSI
- ROSI Express
- ROSI Files
- Safety Abroad Student Registry
- Varsity Blues Registration System
- Web services/APIs
Timetable Builder (Student) will remain available.
A notice will be posted on the ACORN launchpad so that students will be aware of the outage.
Thank you for your patience as we make these improvements.
This email has been sent from a service account and does not accept replies. Please direct any follow up questions to the Enterprise Service Centre http://www.uoft.me/esc
Sincerely,
Student Information Systems
Final Reminder: Feb. 28 Azure Data Studio Retirement – Transition to Visual Studio Code
To: Azure Data Studio Users
From: Enterprise Applications & Solutions Integration
Re: Final Reminder: Feb. 28 Azure Data Studio Retirement – Transition to Visual Studio Code
As a follow-up to earlier communications, this is a final reminder that Microsoft will be retiring Azure Data Studio on February 28, 2026, consolidating its SQL tools in Visual Studio Code.
To maintain security compliance and support, we recommend that current Azure Data Studio users transition to Visual Studio Code. In addition, on May 28, 2026, the connection to all central student data will be disabled.
Resources:
- Instructions to onboard to Visual Studio Code
- Project details and resources
- View a past Connect+Learn session recording
If you have any questions, please visit the Power BI Toolbox and submit a support ticket.
Sincerely,
Reporting and Analytics Technology Team
Enterprise Applications & Solutions Integration
EASI Go Prod AMS & Enterprise Shared Services Updates – Dec. 1, 2025 to Feb. 28, 2026
To: AMS Users
From: Enterprise Applications & Solutions Integration
Re: EASI Go Prod AMS & Enterprise Shared Services Updates – Dec. 1, 2025 to Feb. 28, 2026
Hi everyone,
Enterprise Applications & Solutions Integration (EASI) would like to update you on the latest major production releases and updates for U of T’s Administrative Management Systems (AMS) and Enterprise Shared Services.
The following are major changes from December 1, 2025 to February 28, 2026:
AMS/SAP Technical Platform
Year-End Updates for SAP Human Capital Management (December 6)
On December 6, EASI implemented year-end updates for SAP Human Capital Management (HCM), which are required to ensure that HCM functions include any new legal requirements, tax regulations and payroll updates – all needed for the university’s HR and payroll processing to continue to run smoothly in the new calendar year.
Human Resources Information System
SuccessFactors Recruitment Process (November 14)
On November 14, the HRIS team introduced several improvements to the SuccessFactors recruitment process. These updates make it easier to manage renewals for Adjunct appointments in the Institute of Health Policy, Management and Evaluation. They also included creating a contract process for Adjunct appointments for Public Health Sciences. These enhancements ensure a streamlined experience for administrators and faculty members.
Financial Information System
Concur (February 3)
Concur has been successfully rolled out to all three U of T campuses and the previous expense reimbursement process (ERDD) was formally retired in early February 2026.
Effective February 3, 2026, all expense reimbursement claims must be submitted and processed through Concur. SAP function ZER01 is no longer available for any expense reimbursement claim activity. Any claims in ERDD (web application) that were not fully processed by February 2, 2026 must be re-created in Concur.
The new BMO Travel and Hospitality (T&H) card was also successfully launched and the Procurement team is now accepting applications for new T&H cardholders.
My Research
My Research Funds: Sub-Awards Autopay Program (January 15)
On January 15, EASI and the VPRI launched the Sub‑Awards Autopay program, introducing automated processing for outgoing, VPRI-initiated payments related to research sub‑awards. This new integration between My Research Funds (MRF) and the Financial Information System (FIS) will significantly enhance the timeliness and efficiency of sub-award payments while creating a robust audit trail.
Enterprise Shared Services
ServiceNow Upgrade to Zurich (January 27)
The Enterprise Service Centre Team successfully upgraded the ESC/ServiceNow platform to the Zurich release on January 27. This release brings enhanced performance, greater system stability and improved IT Service Management capabilities.
A major change in this upgrade is the move from Performance Analytics to the new Platform Analytics module. The updated analytics tools offer more flexible dashboards, modernized visualizations and expanded reporting options. Together, these enhancements strengthen the University of Toronto’s ability to monitor service performance and support data‑driven decision‑making across all units.
Sincerely,
Enterprise Applications & Solutions Integration (EASI)
Behind the scenes: U of T upgrades system storing millions of documents
Every day across the University of Toronto, staff submit invoices and purchase orders, retrieve HR data and review research applications. But few realize these activities rely on an invisible digital infrastructure that manages more than 2 million documents.
Information Technology Services (ITS) and partners across U of T recently completed a major overhaul of this critical system, replacing aging technology with a modern, cloud-based platform that improves performance, security and scalability.
“Most people never think about where their documents go when they attach a file in the university’s Administrative Management System,” says Swetlana Signarowski, executive director of Enterprise Applications & Solutions Integration (EASI). “But these documents are essential to the university’s operations and audit trail, and they need to be easily accessible and secure.”
Beyond immediate technical improvements, the migration also advances U of T’s digital transformation strategy by modernizing core administrative systems and improving user experience.
A month-long, round-the-clock migration
The project involved moving over 3.5 terabytes of data to a new platform hosted in Microsoft Azure – a migration that ran overnight for a month to avoid affecting system performance and daily operations.
“Migrating such a large volume of documents required a lot of careful planning,” says Jamal Qureshi, SAP solutions architect with EASI. “We ran migration jobs at night and on weekends to prevent system performance issues, and our team was available for 24/7 monitoring and data validations.”
During the data migration process, the project team verified each record. “If a job was supposed to migrate 10,000 records, we needed to validate those records in the database to ensure accuracy,” says Qureshi.
A modern platform with behind-the-scenes improvements
The previous platform was scheduled for retirement in 2027, offering an opportunity to introduce long-term improvements. While most staff won’t notice changes in how they upload or view attachments, the new solution brings significant enhancements.
“The platform improves performance, collaboration and version control, and strengthens governance and compliance,” says Gary Raposo, associate director AMS/SAP with EASI. “It also introduces advanced metadata management for approved central AMS users to improve search and reporting.”
Metadata is already streamlining work. “With the previous platform, approved users had to navigate to a specific transaction to see attached documents,” says Qureshi. “Now, they can search within SharePoint – so if there are thousands of invoices, it’s easier to search for specific invoice attributes by using metadata.”
The new platform is also integrated with SAP S/4HANA, Microsoft Azure and SharePoint, and supports future cloud initiatives, such as SuccessFactors, and other enterprise applications.
Collaboration across the university
The project required extensive coordination with partners across U of T. The project team worked closely with Financial Services; the Division of People Strategy, Equity and Culture; Procurement Services; Facilities & Services; University Planning, Design & Construction; Vice-President Operations and Real Estate Partnerships; and the Division of the Vice-President, Research & Innovation (VPRI).
“This really was a team effort,” Prashanth Premkumar, project manager with EASI. “Our business partners were essential to the project’s success – especially with testing the new platform. The technical team ensured the migration was successful, and then the business teams validated the accuracy of their files.”
Recognizing the project’s impact on research enablement, Renee Brost, chief administrative officer within the Division of the VPRI, noted: “The migration of research documents to the cloud-based platform was a seamless collaborative effort between VPRI and EASI. This upgrade strengthens the digital foundation that supports U of T’s research enterprise, ensuring researchers and administrators have fast, secure access to key research documents to allow them to focus on advancing research and innovation.”
Raposo adds, “I’d like to thank the SAP operations team, including Praveen Narayanaswamy and Paul Littlefield, for their dedicated work throughout this project. Their knowledge and expertise helped to guide the technical implementation, and they were crucial to the project’s success.”
Next steps
With the migration complete, staff can continue uploading and viewing document attachments as they always have – now on a faster and more secure platform. The upgraded platform ensures critical documents remain accessible and protected for years to come.
“After careful monitoring, the system is stable, fully operational and ready to support U of T’s administrative needs well into the future,” says Signarowski. “This is an important step in building a more resilient digital environment for the university.”
Reminder: Feb. 28 Azure Data Studio Retirement – Transition to Visual Studio Code
To: Azure Data Studio Users
From: Enterprise Applications & Solutions Integration
Re: Reminder: Feb. 28 Azure Data Studio Retirement – Transition to Visual Studio Code
As a follow-up to our initial communications beginning in March 2025, and reiterated in recent communications, this is a reminder that Microsoft will be retiring Azure Data Studio on February 28, 2026, consolidating its SQL tools in Visual Studio Code.
To maintain security compliance and support, we recommend that current Azure Data Studio users transition to Visual Studio Code as soon as possible. In addition, on May 28, 2026, the connection to all central student data will be disabled.
Resources:
-
Join us for a Connect+Learn session on Thursday, February 19 at 11 a.m. or view a past recording.
-
In this session, we will provide:
-
An overview of the migration to Visual Studio Code.
-
An explanation of what’s changing, including key similarities and differences to Azure Data Studio.
-
A demo of how to download and connect to Visual Studio Code.
-
An overview of support resources on the Power BI site.
-
If you have any questions, please visit the Power BI Toolbox and submit a support ticket.
Sincerely,
Reporting and Analytics Technology Team
Enterprise Applications & Solutions Integration
AMS System Maintenance – March 14
To: AMS Users
From: Enterprise Applications & Solutions Integration
Re: AMS System Maintenance – March 14
Dear AMS Users,
Please note that the systems below will be unavailable on Saturday, March 14 from 5 a.m. to 12 p.m. due to system maintenance:
- Academic Administrative Appointments (AAA)
- AMS SAP GUI
- Capital Projects Portal
- Employee Self-Service (ESS)/Manager Self-Service (MSS)
- EvoSuite Applications (EvoOrder, EvoPlan, EvoNotify)
- Fiori Launchpad Reporting
- Invoice Workflow
- My Customer Account
- My Research (MR/Portal)
- SAP Asset Manager Mobile (sync will not work)
- USOURCE
See our System Availability page for a list of ongoing information on system status.
Sincerely,
Enterprise Applications & Solutions Integration (EASI)