{"id":6565,"date":"2021-07-26T06:19:57","date_gmt":"2021-07-26T14:19:57","guid":{"rendered":"https:\/\/officedevblogs.wpengine.com\/?p=6565"},"modified":"2021-07-26T06:19:57","modified_gmt":"2021-07-26T14:19:57","slug":"microsoft-graph-net-sdk-v4-now-generally-available-with-streamlined-authentication-and-more","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-net-sdk-v4-now-generally-available-with-streamlined-authentication-and-more\/","title":{"rendered":"Microsoft Graph .NET SDK\u00a0v4 now generally available with streamlined authentication and more\u00a0"},"content":{"rendered":"

If you\u00a0already work with\u00a0<\/span>Microsoft\u00a0Graph<\/span><\/a>, then you know how powerful it is to\u00a0have a single\u00a0REST\u00a0API to access\u00a0data across\u00a0many\u00a0Microsoft services.\u00a0Microsoft Graph\u00a0.NET\u00a0SDK\u00a0provides\u00a0a fluent API and models\u00a0that\u00a0support retry handling, secure redirects,\u00a0batching requests,\u00a0large file management,\u00a0and\u00a0many\u00a0more\u00a0capabilities.<\/span>\u00a0<\/span><\/p>\n

Today\u00a0we\u2019re announcing the general\u00a0availability (GA) of Microsoft Graph .NET SDK version 4.0.\u00a0<\/span>\u00a0<\/span><\/p>\n

Along with all the\u00a0features and improvements\u00a0discussed\u00a0in the\u00a0<\/span>v4 preview announcement<\/span><\/a>,\u00a0such as single authentication against Microsoft Graph and Azure Identity\u00a0clients\u00a0and\u00a0easy access to response\u00a0information\u00a0through\u00a0the\u00a0<\/span>GraphResponse<\/span><\/b>\u00a0object,\u00a0this GA release\u00a0also\u00a0delivers the new capabilities\u00a0described below.<\/span>\u00a0<\/span><\/p>\n

Rich notifications\u00a0that\u00a0support encrypted content<\/span>\u00a0<\/span><\/h4>\n

The SDK now includes native support to decrypt resource data in rich notifications payloads.<\/span>\u00a0<\/span><\/p>\n

When creating a subscription,\u00a0Microsoft Graph .NET SDK v4\u00a0users can simply use the\u00a0<\/span>AddPublicEncryptionCertificate<\/span><\/b>\u00a0method to add a certificate. Once\u00a0the\u00a0subscription is created,\u00a0use\u00a0the\u00a0<\/span>AreTokensValid<\/span><\/b>\u00a0<\/span><\/i>and\u00a0<\/span>DecryptAsunc<\/span><\/b>\u00a0functions, to\u00a0respectively\u00a0validate\u00a0the\u00a0tokens and decrypt the content\u00a0in the\u00a0notification payload.<\/span>\u00a0<\/span><\/p>\n

Rich notifications provide\u00a0encrypted\u00a0changed data\u00a0along\u00a0with the change notifications, saving the subscriber from having to call back Microsoft Graph\u00a0to fetch the data,\u00a0thereby\u00a0improving application performance. You can read more about this feature in the\u00a0<\/span>documentation<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

Improved testability of<\/span>\u00a0<\/span><\/i>GraphServiceClient<\/span><\/b>\u00a0<\/span><\/h4>\n

The\u00a0<\/span>IGraphServiceClient<\/span><\/b>\u00a0interface has been used by\u00a0Microsoft Graph .NET SDK users\u00a0to build application tests that depend on\u00a0<\/span>GraphServiceClient<\/span><\/b>. Using this interface, however,\u00a0causes\u00a0code breaks whenever the Microsoft Graph metadata changes,\u00a0making it less than ideal for mocking or inheriting.<\/span>\u00a0<\/span><\/p>\n

To improve users’ experience, the interface has been removed in Microsoft Graph .NET SDK v4. Properties and methods of\u00a0<\/span>GraphServiceClient<\/span><\/b>\u00a0have been made virtual, allowing mocking frameworks to\u00a0override them.\u00a0Users do not have to create real objects\u00a0to test the application.<\/span>\u00a0<\/span><\/p>\n

ODataType<\/span><\/b>\u00a0is no longer\u00a0specified by default<\/span>\u00a0<\/span><\/h4>\n

In v4, the\u00a0<\/span>ODataType<\/span><\/b>\u00a0property\u00a0is\u00a0only\u00a0set\u00a0in cases where type disambiguation is\u00a0required,\u00a0for example:<\/span>\u00a0<\/span><\/p>\n

Since\u00a0the release of\u00a0Microsoft Graph .NET SDK v3, generated types\u00a0have\u00a0had\u00a0the\u00a0<\/span>ODataType<\/span><\/b>\u00a0property\u00a0set\u00a0by\u00a0default in\u00a0the SDK.\u00a0Even though this was not a problem\u00a0at\u00a0the\u00a0time,\u00a0Microsoft Graph\u00a0has\u00a0continued\u00a0to grow\u00a0and\u00a0more\u00a0APIs\u00a0have been\u00a0onboarded,\u00a0the\u00a0<\/span>ODataType<\/span><\/b>\u00a0property\u00a0has\u00a0started to\u00a0cause\u00a0<\/span>errors<\/span><\/a>\u00a0during\u00a0its\u00a0serialization\u00a0to some of the APIs.<\/span>\u00a0<\/span><\/p>\n