Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.4

Microsoft Teams

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Microsoft Teams is a collaboration software that combines chat, meetings, calling, collaboration, application integration, and file storage into a single interface. This technology can run in the cloud, over the web, on a Personal Computer or on a Mobile device. This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and authorized by the Mobile Technology and Endpoint Security Engineering Team: https://dvagov.sharepoint.com/sites/OITMT/SitePages/MTHome.aspx The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO This technology must not be downloaded from the Windows App store. This technology is available in two editions: Business and Home. This entry covers both editions.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v25.4
Decision Date:	04/08/2025 at 01:38:26 UTC
Introduced By:	TRM Request
Vendor Name:	Microsoft

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
1.2.x	04/01/2019
1.3.x	03/04/2020
1.4.x	01/30/2021
1.5.x	01/12/2022
1.6.x	03/12/2023
1.7.x (Classic)	01/11/2024
23320.x (New)	12/27/2023
24180.x (New)	07/31/2024
24243.x (New)	09/30/2023
25060.x (New)	03/20/2025

Current Decision Matrix (04/03/2025)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2023

CY2024

CY2025

Future>

Release

1.2.x

Unapproved

Authorized w/ Constraints (POA&M)

1.3.x

DIVEST
[15, 16, 17, 18, 19, 20]

Unapproved

Authorized w/ Constraints (POA&M)

1.4.x

DIVEST
[15, 16, 17, 18, 19, 20]

Unapproved

Authorized w/ Constraints (POA&M)

1.5.x

Approved w/Constraints
[15, 16, 17, 18, 19, 20]

Approved w/Constraints
[15, 16, 17, 19, 20, 21]

DIVEST
[15, 17, 19, 20, 21, 22]

Authorized w/ Constraints (DIVEST)
[15, 17, 19, 20, 21, 22]

Authorized w/ Constraints (POA&M)

1.6.x

Unapproved

Approved w/Constraints
[15, 16, 17, 18, 19, 20]

Approved w/Constraints
[15, 16, 17, 19, 20, 21]

Approved w/Constraints
[15, 17, 19, 20, 21, 22]

DIVEST
[15, 17, 19, 20, 21, 22]

Authorized w/ Constraints (DIVEST)
[15, 17, 19, 20, 21, 22]

Authorized w/ Constraints (POA&M)

1.7.x (Classic)

Unapproved

Approved w/Constraints
[15, 17, 19, 20, 21, 22]

Authorized w/ Constraints
[15, 17, 19, 20, 21, 22]

Authorized w/ Constraints (DIVEST)
[15, 17, 19, 20, 21, 22]

Authorized w/ Constraints (POA&M)

23320.x (New)

Unapproved

Approved w/Constraints (PLANNING/EVALUATION)
[1, 15, 17, 19, 20, 21, 22]

Authorized w/ Constraints (DIVEST)
[15, 17, 19, 20, 21, 22]

Authorized w/ Constraints (POA&M)

24180.x (New)

Unapproved

Authorized w/ Constraints (DIVEST)
[15, 17, 19, 20, 21, 22]

Authorized w/ Constraints (POA&M)

24243.x (New)

Unapproved

Authorized w/ Constraints
[15, 17, 19, 20, 21, 22]

Authorized w/ Constraints (DIVEST)
[15, 19, 20, 21, 22, 23]

25060.x (New)

Unapproved

Authorized w/ Constraints (POA&M)

Authorized w/ Constraints
[15, 19, 20, 21, 22, 23]

Note:

At the time of writing, version 25060.203.3471.5023 is the most current version, released 03/20/2025.

A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 24243.1309.3132.617, and version 25044.2208.3471.2155 is under testing and development for six weeks from 03/26/2025, all Classic versions will be removed.

Decision Constraints


[15]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[16]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[17]	This technology must not be updated silently. This technology must not be downloaded from the Windows App store. Per the Initial Product Review, users must abide by the following constraints: Microsoft Teams must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches. Ensure VA sensitive data, stored and transmitted in Microsoft Teams systems, is encrypted using FIPS 140-2 certified cryptographic module. If that is not technically possible then 3rd party encryption methods must be employed. Any plug-in, application, or service that interacts with the Teams client must be vetted by the VA Enterprise Messaging, Collaboration, Authentication and Office 365 Services (EMCAO) team.

[18]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[19]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[20]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations.

[21]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[22]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[23]	This technology must not be updated silently. This technology must not be downloaded from the Windows App store. Per the Initial Product Review, users must abide by the following constraints: Microsoft Teams Desktop Client will require a 3rd party FIPS 140-2 certified (or its successor) solution for any data containing PHI/PII or VA sensitive information. Microsoft Teams must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches. Ensure VA sensitive data, stored and transmitted in Microsoft Teams systems, is encrypted using FIPS 140-2 certified (or its successor) cryptographic module. If that is not technically possible then 3rd party encryption methods must be employed. Any plug-in, application, or service that interacts with the Teams client must be vetted by the OIT Connectivity and Collaboration Services (CCS) office.

Name	Description
No components have been identified for this entry.


Collaboration and Electronic Workplace Collaboration Software	Real-Time and Team Collaboration
Network and Telecommunications Transport	Telecommunications

General Analysis

Adoption Benefits

This technology is backed by an industry leading vendor.
This technology has a comprehensive set of documentation.

Adoption Risks

This technology has the potential to collect, store, or transmit Protected Health Information (PHI)/Personally Identifiable Information (PII) data.
There are known Common Vulnerabilities and Exposures (CVEs) and VA Cyber Security Operations Center (CSOC) vulnerabilities. Please see https://nvd.nist.gov/vuln/search for more details.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
IPR/SAR Adoption Risk - The product is not Federal Information Processing Standards (FIPS) 140-2 (or its successor) certified.
IPR/SAR Adoption Risk - There are a published vulnerabilities including CVE-2024-42004, CVE-2024- 41145, CVE-2024-41138, CVE-2024-38197 of this software.
IPR/SAR Adoption Risk - This technology has the potential to collect, store, or transmit Protected Health Information (PHI)/Personally Identifiable Information (PII) data.
IPR/SAR Adoption Risk - As noted in the features section, users have the ability to customize the client by adding both Microsoft and third-party applications and services via the built-in client App function.
This technology is available as freeware. If commercial support is not purchased, the product will be without clearly defined support options which may result in suboptimal enterprise level support.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.

Architectural Benefits

This technology can integrate with other Microsoft applications.
This technology is portable as it runs on multiple TRM-authorized operating systems.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.
This technology can be updated silently.

- The information contained on this page is accurate as of the Decision Date (04/08/2025 at 01:38:26 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.4

General Information

Vendor Release Information

Current Decision Matrix (04/03/2025)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 25.4

General Information

Vendor Release Information

Current Decision Matrix (04/03/2025)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework