How doe the anti-impersonation feature work?

The anti-impersonation feature uses artificial intelligence to distinguish between messages from legitimate senders and impersonated senders. This feature also checks emails originating from non-U of T email addresses against a pre-defined list of display names belonging to senior leaders at U of T. This means that if someone attempts to impersonate a senior leader by spoofing/using their name or email address to contact U of T recipients, the scam email will be sent directly to users’ junk folders.

To learn more about the anti-impersonation feature, please review the article Secure U of T advanced threat protections: anti-phishing protection.

Who will have access to the data collected for security threat protection purposes?

Access to information is limited to authorized information security staff who are required to sign a confidentiality agreement with the university as part of a formal access request and approval process. Additionally, Microsoft security tools use artificial intelligence to analyze data and designated staff interact with the data only when a threat alert is triggered.

Microsoft employees do not interact with data unless they are directly engaged by the University for assistance and troubleshooting. Aggregate data may be used by Microsoft for service improvement purposes but only in a manner where it is not linked to any identifiable individual.

Will my activity and personal use of device(s) be tracked?

Individual’s personal use of University networks or devices will not be monitored.  Data collected will only be used for protection against security threats and will not be used to support investigations related to employee productivity, attendance/activity and/or any other general monitoring of behaviour not directly associated with security threat protection at the University.

Will my activity and personal use of device(s) be tracked?

Individual’s personal use of University networks or devices will not be monitored.  Data collected will only be used for protection against security threats and will not be used to support investigations related to employee productivity, attendance/activity and/or any other general monitoring of behaviour not directly associated with security threat protection at the University.

What is happening to content stored on Confluence Server?

Confluence Server will reach end of life on February 15, 2024. In advance of this deadline, we are working to migrate all current Confluence Server users and content to Confluence Cloud by January 29, 2024.

Please note:

  • Upon launch, wiki.easi.utoronto.ca will redirect to https://its-uoft.atlassian.net/ and bookmark links to individual Confluence Server pages will need to be updated manually. This new URL will only be activated upon launch.
  • When logging in to Confluence Cloud, you will be prompted to sign in using the same credentials as Microsoft 365.
  • After the migration, you may notice some feature, terminology, and interface differences. Check out this quick start guide(s) for a preview of those changes: Quick start guide for Confluence Cloud 
  • You can view Atlassian’s curated list of training resources to help you get comfortable quickly.

What can I do with a free Azure DevOps Stakeholder license?

Stakeholders are users with free but limited access to Azure DevOps features and functions. With Stakeholder access, you can add and modify work items, manage build and release pipelines, and view dashboards. You can check project status and provide direction, feedback, feature ideas, and business alignment to a team.