What kinds of applications can I request through the ARC?

University staff and faculty can request that third-party applications and add-ins that connect with their Microsoft 365 accounts be enabled. These requests are subject to a formal review process.

If you are requesting one of the following applications, please purchase a license through the Library. There is no need to submit a request through the Application Review Committee:

  • Microsoft Power BI Pro
  • Microsoft Project
  • Microsoft Visio

Why are some approved applications available to everyone, and why are some user restricted?

The availability of an approved application depends on its risk status. Two types of apps and add-ins can be implemented as part of the approval process:

    • Low-risk apps: Identified low-risk applications that do not access Microsoft 365 data are available for University-wide use. 
    • Higher risk apps: Applications that are higher risk and integrate with Microsoft 365 data can be enabled for specific user groups after going through a request and approval process. 

If you would like access to a higher risk application, please submit a request through the Enterprise Service Centre. 

Can I request an EASI application through the ARC?

No. Applications developed by EASI do not currently require an information risk assessment (IRM), but they do require a privacy impact assessment (PIA). These applications have an existing governance process and are outside the scope of the Application Review Committee.

Why do application requests need to go through the ARC?

Applications that integrate with University Microsoft 365 accounts must go through a formal request and review process. The review process looks at the application, its intended function and whether similar applications have already been approved. It also includes a risk assessment that specifically examines the type of account information the app will have access to once it is installed by a user. The review process is an important part of promoting the sustained efficacy and security of possible third party application solutions.

What happens to chat threads that are created during a meeting?

  • If you intend to save chats from Teams meetings, the meeting must be created from inside a Team channel. These chats are not affected by the new retention protocol. Please refer to the knowledge base article, Creating a meeting from a Microsoft Teams Channel, to learn how to create a meeting from inside a Teams Channel. 
  • One way to save ideas and action items from a Teams meeting recording is by summarizing the meeting transcript and saving it on a Teams Channel or any other preferred location. Please refer to the knowledge base article, Using U of T Protected Copilot Chat to Summarize and Publish Meeting notes, to learn how to summarize recorded meeting transcripts using U of T Protected CoPilot and save it.
  • If there is no intent to preserve the meeting chat, it is not necessary to create the meeting inside a Team or record it. 

Does the 30-day retention policy also apply to Chats to yourself?

Yes, messages sent to yourself will also be subject to deletion by the retention policy.

The retention policy affects all direct chats including the messages users send to themselves. Teams treats messages sent to your own account similarly to those sent to other users in terms of storage and retentions.

What is a designated Microsoft Teams channel

A designated Teams channel refers to a specific channel within a Microsoft Teams team that is set aside for a particular purpose or topic. Channels in Microsoft Teams are dedicated sections that help organize conversations, files, and tools around various subjects, projects, or disciplines, making collaboration more structured and efficient.

Here are some key points about channels in Microsoft Teams:

  • Channels sit inside of teams: They are part of the broader team and are used for conversations and sharing related to a specific topic, department, or project.
  • Types of channels: There are standard channels open to all team members, private channels for confidential discussions, and shared channels for collaboration with people inside and outside your organization.
  • General channel: Every team has a General channel, which is the default channel for team-wide communication and cannot be deleted.
  • Organization: Channels can be organized by anything relevant to the team, such as group, project, feature, etc., and are designed to keep the team’s work focused and organized.

What Can I do to prepare for this change?

There are a few steps you can start taking: 

  • First, review your chat history. You will need a lot of time for this! 
  • Search your chat history and ensure that you copy and save those threads that are important to you before September 30, 2024. All messages older than 30 days will be affected. 
  • Identify any relevant files that have been shared over one-on-one or group chats in Teams and move them from your OneDrive Teams chat folder into another relevant folder. If it’s a file that is shared and collaborated on, consider moving it into a Teams channel folder or SharePoint site. 
  • Keep an eye out for future communications
  • Watch recordings of our information sessions – Scroll down this webpage to watch recordings of our information sessions.
  • Spread the word!