Contact Us 1-800-596-4880

Microsoft Teams Connector Release Notes - Mule 4

Support Category: Select

Anypoint Connector for Microsoft Teams (Microsoft Teams Connector) gives you access to the Microsoft Teams APIs. This connector exposes the most commonly used operations provided by the Microsoft Teams API.

1.1.4

March 28, 2024

What’s New

  • This connector is now compatible with Java 17.

Compatibility

Software Version

Anypoint Studio

7.3.5 and later

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Microsoft Graph Rest API

v1

OData API

v4

1.1.3

August 23, 2023

Compatibility

Software Version

Anypoint Studio

7.3.5 and later

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4

Fixed Issues

Issue Resolution ID

The connector now handles the Lifetime validation failed, the token is expired error correctly and refreshes the access token.

W-13903204

1.1.2

October 13, 2022

Compatibility

Software Version

Anypoint Studio

7.3.5 and later

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4

Fixed Issues

Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853414

1.1.1

April 4, 2022

Compatibility

Software Version

Anypoint Studio

7.3.5 and later

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4

Fixed Issues

Issue ID

Improved connection validation.

W-10887274

Fixed a security vulnerability.

W-10920474

1.1.0

March 21, 2022

What’s New

  • The TLS configuration parameters in the OAuth 2.0 Authorization Code and OAuth 2.0 Client Credentials connections are now deprecated.

Compatibility

Software Version

Anypoint Studio

7.3.5 and later

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4

1.0.3

January 5, 2022

Compatibility

Software Version

Anypoint Studio

7.3.5 and later

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4

Fixed Issues

Issue ID

Upgraded library dependencies.

CONN-9847

Known Issues

  • When offline_scope is not specified in the Microsoft OAuth Code Grant Config and the access token is expired, the connector throws a MULE:UNKNOWN error instead of a TEAMS:INVALID_CONNECTION error.

1.0.2

December 7, 2021

Compatibility

Software Version

Anypoint Studio

7.3.5 and later

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4

Fixed Issues

Issue ID

Fixed reported security vulnerabilities.

CONN-9254

Known Issues

  • When offline_scope is not specified in the Microsoft OAuth Code Grant Config and the access token is expired, the connector throws a MULE:UNKNOWN error instead of a TEAMS:INVALID_CONNECTION error.

1.0.1

June 4, 2021

Compatibility

Software Version

Anypoint Studio

7.3.5 and later

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4

Fixed Issues

  • Optimized the connector to improve its overall stability and performance.

Known Issues

  • When offline_scope is not specified in the Microsoft OAuth Code Grant Config and the access token is expired, the connector will throw a MULE:UNKNOWN error instead of a TEAMS:INVALID_CONNECTION error.

1.0.0

February 26, 2021

New connector.

Compatibility

Software Version

Anypoint Studio

7.3.5 and later

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4

Features

For a list of supported configurations and operations, see the Microsoft Teams Connector Reference Guide.

Fixed in This Release

Not applicable.

Known Issues

  • This connector is not FIPS 140 compliant.

  • The TLS handshake does not work when performing access token retrieval.

  • The proxy configuration is not taken into account when performing access token retrieval.

  • The refresh token mechanism for the OAuth 2.0 authorization code grant type only works if the offline_access scope is added.