/
Microsoft Teams

Microsoft Teams

Documentation



From: "Smith, John L." <jsmithjr@purdue.edu>
Date: Monday, November 23, 2020 at 3:29 PM

All ITaP Personnel,    

As of Tuesday, Nov 24th at approximately noon, you have permissions to create Microsoft Office 365 Teams.  This is part of a pilot, before rolling out this ability to all faculty and staff before next semester. 

If you create Microsoft Teams, it is important to follow the naming standards outlined below.  

Also, support and training information is listed below. Note that certain types of data cannot be stored or used in Microsoft Teams per Purdue data handling guidelines. 

Please use normal channels to provide feedback and get support as a part of this implementation.



General Teams Documentation

Teams Guidelines for Staff

Following is additional guidance and information regarding the Teams application’s overall usage:

Microsoft Teams is a cloud-based collaboration application that is part of Office 365. As a cloud-based tool, Microsoft regularly makes improvements and adds features to Teams and related applications. Due to its dynamic nature and extensive capabilities, the best user support and answers to user questions are available from Microsoft, which has many Teams resources on the web. A good starting point is: https://support.office.com/en-us/teams.

ITaP Support of Teams:

ITaP provides support of Teams regarding availability of the infrastructure and assistance on resolution of major functionality issues.  Training and general usage support is provided by Microsoft.  ITaP has worked with Microsoft to arrange for Purdue specific training in the past and will likely do so in the future depending on availability. Purdue’s user support for Teams is limited. If you have a question related to the Purdue infrastructure required to make Teams available, please contact your campus unit’s IT staff directly or via the ITaP help desk.

Data Handling

NOTE: certain types of data cannot be stored or used in Microsoft Teams per Purdue data handling guidelines. 

NOTE: Storing Export Control data on the Teams platform has been specifically disallowed by the controlling authority.

Use of Microsoft Teams at Purdue is NOT recommended or validated for restricted data. Restricted data (e.g. protected health information, banking information, or credit card information) may be subject to laws that require the data to be stored in an encrypted form or require the data to be limited to access by specific authorized users only. Some common laws that may come into play include HIPAA (for health information), FERPA (for student information), GLBA (for financial account information), and PCI (for credit card information). Contact your data steward, https://www.purdue.edu/securepurdue/data-handling/data-stewards.php, if you have questions about how these laws may apply to the data you are using. You can view ITaP's security statement for the Office 365 suite, including Teams, at https://support.purdue.edu/goldanswers/596456.



Teams Creation Documentation

Teams Creation by ITaP Staff

Naming conventions:

NOTE: Be specific in your Team names, there should always be some form of department indicator.

When creating Teams, please keep in mind that other areas may have similar roles, job functions, or positions.  A common example we've seen in years past would be "Business Office"; nearly every department has one, yet when creating mailboxes and lists we often see requests of just "Business Office".  Try to be descriptive, possibly starting the Team name with your Department code like "Krannert Business Office", "Vet Business Office", etc.  Other common examples like "IT Staff", "Printers", "Help Desk", and so on should always be prefaced with your Department code as well. 

NOTE: Class teams should include semester & course name.

For Class Teams, be aware that “PSY 120” will most likely have multiple sessions taught by different professors.  Also note that the Teams you create will remain in place for at least 13 months, so it would be a good idea to name those Teams according to the semester and session.  The Mailman lists are created with names like “spring-2020-psy-session”, so you may consider incorporating the semester/year/session into the Team name to differentiate between classes.

NOTE: Use good judgement when wording your team names.

It also goes without saying, but please refrain from using any questionable words.  While we do have certain blocks in place for common swear words and University departments (President, Registrar, etc), we’ll rely on your judgement for professional language being used.

4 Team Types available:

URL's for creating Teams, definitions of types of Teams available:

Before creating a new Team, you may want to familiarize yourself with the four types available to Education tenants, and what comes with each type of Team.  A table view of the four types with permissions and features can be seen here:

https://support.office.com/en-us/article/choose-a-team-type-to-collaborate-in-microsoft-teams-0a971053-d640-4555-9fd7-f785c2b99e67


At the bottom of that same page are links for creating Teams for Classes, Staff, and Professional Learning Community (PLC).  Below are the URL’s for each of them:

Class:  https://support.office.com/en-us/article/create-a-class-team-in-microsoft-teams-fae422eb-58b7-4431-9ff2-a4b9b6ae7c5b

Staff:  https://support.office.com/en-us/article/create-a-staff-team-in-microsoft-teams-314ac9d5-36a9-408e-8ae4-7ef20e9f1ddf

PLC:  https://support.office.com/en-us/article/create-a-plc-team-in-microsoft-teams-ad803fa2-c967-41b4-ae37-0bf60f17fa00

Other:  



Teams Training Documentation




Teams Office 365 Portal Documentation






Teams Client Application Documentation

Unable to log into Teams Client Application - Trusted Platform Module (TPM) Error

"We're sorry - We've run into an issue."

Issue: 

User tries to open teams, and gets this error →

This, and similar issues with Outlook, and Bitlocker SEEM to be related to issues with the computer's TPM (Trusted Platform Module) chip on the motherboard.


Workaround: (Still needs verified/authorized by CSDS)

Not an actual fix, but hopefully a workaround, probably should be escalated to CSDS_SUPPORT. Teams is still very new to us all, so we're still figuring it out.

  • Close teams and Outlook
  • We're gonna try to 'reboot' BitLocker by suspending it to see if we can get it out of it's stall
  • Check to see if it's working now


Related content

Microsoft Teams Support
Microsoft Teams Support
More like this