{"id":4077,"date":"2020-02-04T15:00:54","date_gmt":"2020-02-04T22:00:54","guid":{"rendered":"https:\/\/developer.microsoft.com\/en-us\/office\/blogs\/?p=4077"},"modified":"2020-02-04T15:00:54","modified_gmt":"2020-02-04T22:00:54","slug":"microsoft-graph-subscriptions-deprecating-tls-1-0-and-1-1","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-subscriptions-deprecating-tls-1-0-and-1-1\/","title":{"rendered":"Microsoft Graph subscriptions to change notifications \u2013 deprecating TLS 1.0 and 1.1"},"content":{"rendered":"

Following\u00a0<\/span>earlier\u00a0<\/span>announcements from\u00a0<\/span>Apple<\/span><\/a>,\u00a0<\/span>Google<\/span><\/a>,\u00a0<\/span>Microsoft<\/span><\/a>, and\u00a0<\/span>Mozilla<\/span><\/a>\u00a0and a global continuing trend to deprecate TLS 1.0 and 1.1<\/span>,\u00a0<\/span>subscribers\u00a0<\/span>of\u00a0<\/span>change notifications o<\/span>n<\/span>\u00a0user data\u00a0<\/span>should<\/span>\u00a0take note<\/span>.<\/span>\u00a0<\/span>Starting\u00a0<\/span>May 15<\/span>th<\/span>, 2020<\/span>,<\/span>\u00a0<\/span>subscribers<\/span>\u00a0<\/span>who use\u00a0<\/span>notification<\/span>\u00a0endpoint<\/span>s\u00a0<\/span>that\u00a0<\/span>only support TLS 1.0 or TLS 1.1 will stop receiving\u00a0<\/span>notifications<\/span>,<\/span>\u00a0unless they upgrade\u00a0<\/span>their\u00a0<\/span>infrastructure<\/span>\u00a0<\/span>to\u00a0<\/span>compliance and\u00a0<\/span>support TLS 1.<\/span>2<\/span>.<\/span>\u00a0<\/span><\/p>\n

S<\/span>ecurity and privacy\u00a0<\/span>are key<\/span>\u00a0commitments<\/span>\u00a0<\/span>that Microsoft makes to our customers.<\/span>\u00a0<\/span>E<\/span>arlier\u00a0<\/span>versions of TLS\u00a0<\/span>make it challenging for us to\u00a0<\/span>live up to\u00a0<\/span>these commitments.<\/span>\u00a0<\/span><\/p>\n

We\u2019re introducing a new\u00a0<\/span>latestSupportedTlsVersion<\/span><\/b>\u00a0property on the\u00a0<\/span>subscription<\/span><\/a>\u00a0entity\u00a0<\/span>to\u00a0<\/span>let our customers\u00a0<\/span>gradually\u00a0<\/span>transition<\/span>\u00a0to TLS<\/span>\u00a0<\/span>1.2.<\/span>\u00a0<\/span><\/p>\n

S<\/span>ubscriptions created with\u00a0<\/span>both\u00a0<\/span>the v<\/span>1.0 and the beta\u00a0<\/span>endpoints are impacted by th<\/span>is<\/span>\u00a0change.<\/span>\u00a0<\/span><\/p>\n

How does this affect me<\/span>?<\/span>\u00a0<\/span><\/h3>\n

If your application implement<\/span>s\u00a0<\/span>change notifications<\/span><\/a>\u00a0and\u00a0<\/span>the notification endpoint\u00a0<\/span>(as specified by\u00a0<\/span>the<\/span>\u00a0<\/span>notification<\/span><\/b>URL<\/span><\/b>\u00a0<\/span><\/b>property)<\/span>\u00a0<\/span>does not support TLS 1.2, you\u00a0<\/span>must<\/span>\u00a0upgrade your infrastructure in order to keep receiving notifications.<\/span>\u00a0<\/span><\/p>\n

You can test\u00a0<\/span>your endpoints using the\u00a0<\/span>SSL\u00a0<\/span>server test tool<\/span><\/a>\u00a0provided by SSL Labs.<\/span>\u00a0After\u00a0<\/span>you run\u00a0<\/span>the\u00a0<\/span>test, if\u00a0<\/span>TLS 1.2\u00a0<\/span>in\u00a0<\/span>the\u00a0<\/span>Configuration<\/span><\/b>\u00a0section\u00a0<\/span>is<\/span>\u00a0set to\u00a0<\/span>yes<\/span><\/b>,<\/span>\u00a0you\u00a0<\/span>don\u2019t<\/span>\u00a0need to take any action.<\/span>\u00a0<\/span><\/p>\n

If th<\/span>is<\/span>\u00a0protocol\u00a0<\/span>is\u00a0<\/span>set to\u00a0<\/span>no<\/span><\/b>,<\/span>\u00a0<\/span>you need to upgrade\u00a0<\/span><\/b>your infrastructure to support<\/span><\/b>\u00a0<\/span><\/b>TLS 1.2<\/span><\/b>.<\/span>\u00a0<\/span><\/p>\n

Key dates<\/span>\u00a0<\/span><\/h3>\n

Starting on February 1<\/span><\/b>7<\/span><\/b>, 2020<\/span><\/b>:<\/span><\/b>\u00a0<\/span><\/p>\n