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.
Safe Attachments works to identify malicious files/attachments. Files identified as malicious are blocked and a warning is displayed, preventing end user devices from getting infected.
To learn more about the Safe Attachments feature, please review the article Secure U of T advanced threat protections: Safe Attachments for email, OneDrive, SharePoint and Teams.
The Safe Links feature scans links for potentially malicious content when they are clicked on by a user. A warning is displayed if a link is determined to be malicious.
To learn more about the Safe Links feature, please review the article Secure U of T advanced threat protections: Safe Links for email, Teams and documents.
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.
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.
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.
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.
Records from Jira Server will remain as a read-only online archive until February 3, 2025, with access limited to team leads. Specific Jiras can be copied from Jira to Azure DevOps manually on an as-needed basis.
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.
Divisions working independently of EASI will receive a quarterly charge from Business Operations & Administration (BOA). BOA will perform a cost analysis and will request a funds transfer from divisional CAOs.
Azure DevOps licenses will cost approximately CAD $8/month per user (costs are subject to change per Microsoft’s discretion) and stakeholder licenses are free. Learn more about pricing options.