Set up change notifications that include resource data (preview)

Microsoft Graph allows apps to subscribe to change notifications for resources via webhooks. You can now set up subscriptions to include the changed resource data (such as the content of a Microsoft Teams chat message) in change notifications. Your app can then run its business logic without having to make a separate API call to fetch the changed resource. As a result, the app performs better by making fewer API calls, which is beneficial in large scale scenarios.

Including resource data as part of change notifications requires you to implement the following additional logic to satisfy data access and security requirements:

  • Handle special subscription lifecycle notifications to maintain an uninterrupted flow of data. Microsoft Graph sends lifecycle notifications from time to time to require an app to re-authorize, to make sure access issues have not unexpectedly cropped up for including resource data in change notifications.
  • Validate the authenticity of change notifications as having originated from Microsoft Graph.
  • Provide a public encryption key and use a private key to decrypt resource data received through change notifications.

Resource data in notification payload

In general, this type of change notifications include the following resource data in the payload:

  • ID and type of the changed resource instance, returned in the resourceData property.
  • All the property values of that resource instance, encrypted as specified in the subscription, returned in the encryptedContent property.
  • Or, depending on the resource, specific properties returned in the resourceData property. To get only specific properties, specify them as part of the resource URL in the subscription, using a $select parameter.

Supported resources

Currently, the Microsoft Teams chatMessage (preview) resource supports change notifications that include resource data. Specifically, you can set up a subscription that applies to one of the following:

  • New or changed messages in a specific Teams channel: /teams/{id}/channels/{id}/messages
  • New or changed messages in a specific Teams chat: /chats/{id}/messages

The chatMessage resource supports including all the properties of a changed instance in a change notification. It does not support returning only selective properties of the instance.

This article walks through an example of subscribing to change notifications of messages in a Teams channel, with each change notification including the full resource data of the changed chatMessage instance.

Creating a subscription

To have resource data included in change notifications, you must specify the following properties, in addition to those that are usually specified when creating a subscription:

  • includeResourceData which should be set to true to explicitly request resource data.
  • lifecycleNotificationUrl which is an endpoint where lifecycle notifications are delivered. This can be the same or different as notificationUrl.
  • encryptionCertificate which contains only the public key that Microsoft Graph uses to encrypt resource data. Keep the corresponding private key to decrypt the content.
  • encryptionCertificateId which is your own identifier for the certificate. Use this ID to match in each change notification, which certificate to use for decryption.

Keep the following in mind:

  • Use the same host name for both change notification endpoints (notificationUrl and lifecycleNotificationUrl).
  • Validate both endpoints as described here. If you choose to use the same URL for both endpoints, you will receive and respond to two validation requests.
  • You cannot update (PATCH) an existing subscription to add the lifecycleNotificationUrl property. You should remove the existing subscription, and create a new subscription to include the lifecycleNotificationUrl property.

Subscription request example

The following example subscribes to two types of notifications:

  • Resource changes - channel messages being created or updated in Microsoft Teams
  • Subscription lifecycle events which can affect the flow of change notifications. See more details about lifecycle notifications in the next section.
Content-Type: application/json
  "changeType": "created,updated",
  "notificationUrl": "",
  "lifecycleNotificationUrl": "",
  "resource": "/teams/{id}/channels/{id}/messages",
  "includeResourceData": true,
  "encryptionCertificate": "{base64encodedCertificate}",
  "encryptionCertificateId": "{customId}",
  "expirationDateTime": "2019-09-19T11:00:00.0000000Z",
  "clientState": "{secretClientState}"

Subscription response

HTTP/1.1 201 Created
Content-Type: application/json

  "changeType": "created,updated",
  "notificationUrl": "",
  "lifecycleNotificationUrl": "",
  "resource": "/teams/{id}/channels/{id}/messages",
  "includeResourceData": true,
  "encryptionCertificateId": "{custom ID}",
  "expirationDateTime": "2019-09-19T11:00:00.0000000Z",
  "clientState": "{secret client state}"

Subscription lifecycle notifications

Certain events can interfere with change notification flow in an existing subscription. Subscription lifecycle notifications inform you actions to take in order to maintain an uninterrupted flow. Unlike a resource change notification which informs a change to a resource instance, a lifecycle notification is about the subscription itself, and its current state in the lifecycle.

Lifecycle notifications are delivered to the lifecycleNotificationUrl.

In this section:

Lifecycle notification that challenges subscription authorization

One type of lifecycle notifications challenges the authorized state of an active subscription. When the lifecycleEvent property in a notification indicates reauthorizationRequired, you must re-authorize the subscription to maintain the data flow.

When you create a long-lived subscription (for example, one that lasts for 3 days), change notifications flows to the location indicated in notificationUrl. However, at any point in time, Microsoft Graph may require that you re-authorize the subscription to prove that you still have access to resource data, in case the conditions of access have changed since the subscription was created. The following are examples of changes that affect your access to data:

  • A tenant administrator may revoke your app's permissions to read a resource.
  • In an interactive scenario, the user who provides the authentication token to your app may be subject to dynamic policies based on various factors, such as their location, device state, or risk assesment. For example, if the user changes their physical location, the user may no longer be allowed to access the data, and your app will not be able to re-authorize the subscription. For more information on dynamic policies that control access, see Azure AD conditional access policies.

Authorization challenge flow

The flow of an authorization challenge for an active, non-expired subscription looks as follows:

  1. Microsoft Graph requires a subscription to be re-authorized

    The reasons for this may vary from resource to resource, and may change over time. Regardless of the cause of the re-authorization event, you will need to respond to it.

  2. Microsoft Graph sends an authorization challenge notification to the lifecycleNotificationUrl

    Note that the flow of change notifications may continue for a while, giving you extra time to respond. However, eventually change notification delivery will pause, until you take the required action.

  3. Respond to this lifecycle notification in one of two ways:

    1. Re-authorize the subscription. This does not extend the expiry date of the subscription.
    2. Renew the subscription. This both re-authorizes and extends the expiry date.

    Note: Both actions require you to present a valid authentication token, similar to creating a new subscription or renewing a subscription before its expiry.

  4. If you successfully re-authorize or renew the subscription, change notifications continue. Otherwise, change notifications remain paused.

Example authorization challenge

Below is an example lifecycle notification that requests re-authorizing a subscription.

Note the following:

  • The "lifecycleEvent": "reauthorizationRequired" field identifies this notification as an authorization challenge.
  • The lifecycle notification does not contain any information about a specific resource, because it is not related to a resource change, but to the subscription state change.
  • Similar to change notifications, you can batch lifecycle notifications together (in the value collection), each with a possibly different lifecycleEvent value. Process each lifecycle notification in the batch accordingly.
  "value": [
      "lifecycleEvent": "reauthorizationRequired",
      "subscriptionId": "e3898f08-5cd0-4a6a-80fc-6addbfb73b7b",
      "subscriptionExpirationDateTime": "2019-09-18T00:52:45.9696658+00:00",
      "clientState": "{secret client state}",
      "tenantId": "84bd8158-6d4d-4958-8b9f-9d6445542f95"

Note: for a full description of the data sent when change notifications are delivered, see changeNotificationCollection.

Responding to an authorization challenge

Take the following steps to process an authorization challenge lifecycle notification. The first two steps of acknowledging and validating the lifecycle notification is similar to responding to a resource change notification.

  1. Acknowledge the receipt of the lifecycle notification, by responding to the POST call with HTTP 202 Accepted.

  2. Validate the authenticity of the lifecycle notification. Further details below.

  3. Ensure the app has a valid access token to take the next step.

    If you are using one of the authentication libraries, the library handles this for you by either reusing a valid cached token, or obtaining a new token from prompting the user to log in again with a new password. However, obtaining a new token may fail, since the conditions of access may have changed, and the user may no longer be allowed access to the resource data.

  4. Call either of the following two APIs. If the API call succeeds, the change notification flow resumes.

    • Call the /reauthorize action to re-authorize the subscription without extending its expiration date:

      Content-type: application/json
    • Perform a regular renew action to re-authorize and renew the subscription at the same time:

      Content-Type: application/json
         "expirationDateTime": "2019-09-21T11:00:00.0000000Z"

      Renewing may fail, because the authorization checks performed by the system may deny the app or the user access to the resource. It may be necessary for the app to obtain a new access token from the user to successfully re-authorize a subscription.

      You may retry these actions later, at any time, and succeed if the conditions of access change. Any notifications about resource changes that happen between the time the lifecycle notification was sent, and the time when the app eventually re-creates the subscription successfully, would be lost. In such cases, the app should separately fetch those changes.


Keep the following in mind:

  1. Authorization challenges do not replace the need to renew a resource change subscription before it expires.

    While you can choose to renew a subscription when you receive an authorization challenge, Microsoft Graph may not challenge all of your subscriptions. For example, a subscription that does not have any activity and has no change notifications pending delivery may not signal any re-authorization challenges to your app. Make sure to renew subscriptions before they expire.

  2. The frequency of authorization challenges is subject to change.

    Do not make assumptions about the frequency of authorization challenges. These lifecycle notifications tell you when to take actions, saving you from having to track which subscriptions require re-authorization. Be ready to handle authorization challenges anywhere from once a few minutes for every subscription, to rarely for only some of your subscriptions.

Future-proof your code to handle other types of lifecycle notifications

Expect subscription lifecycle notifications to be posted to the same endpoint specified by lifecycleNotificationUrl. They differentiate by the lifecycleEvent property and may contain slightly different schema and properties to serve the scenarios they address.

Implement your code in anticipation of new types of lifecycle notifications:

  1. Use the lifecycleEvent property to identify the type of notification so to determine the appropriate response. For example, look for the "lifecycleEvent": "reauthorizationRequired" property to identify a specific event, and handle it.

  2. Log any lifecycle events that your app does not recognize to gain awareness.

  3. Subscribe to the Microsoft Graph Developer Blog to watch for announcements of lifecycle notifications for new scenarios.

  4. Look up related documentation for new lifecycle notifications and implement support for them as appropriate.

Validating the authenticity of notifications

Apps often execute business logic based on resource data included in change notifications. Having first verified the authenticity of each change notification is important. Otherwise, a third party could spoof your app with false change notifications, make it execute its business logic incorrectly, and lead to a security incident.

For basic change notifications which do not contain resource data, simply validate them based on the clientState value as described here. This is acceptable, as you can make subsequent trusted Microsoft Graph calls to get access to resource data, and therefore the impact of any spoofing attempts is limited.

For change notifications that deliver resource data, perform a more thorough validation before processing the data.

In this section:

Validation tokens in the change notification

A change notification with resource data contains an additional property, validationTokens, which contains an array of JWT tokens generated by Microsoft Graph. Microsoft Graph generates a single token for each distinct app and tenant pair for whom there is an item in the value array. Keep in mind that change notifications may contain a mix of items for various apps and tenants that subscribed using the same notificationUrl.

In the following example, the change notification contains two items for the same app, and for two different tenants, therefore the validationTokens array contains two tokens that need to be validated.

	"value": [
			"subscriptionId": "76619225-ff6b-4489-96ca-4ef547e78b22",
      "tenantId": "84bd8158-6d4d-4958-8b9f-9d6445542f95",
			"changeType": "created",
			"subscriptionId": "e990d58f-fd93-40af-acf7-a7c907c5d8ea",
      "tenantId": "46d9e3bd-6309-4177-a016-b256a411e30f",
			"changeType": "created",
	"validationTokens": [

Note: for a full description of the data sent when change notifications are delivered, see changeNotificationCollection.

How to validate

If you're new to token validation, see Principles of Token Validation for an overview. Use an SDK, such as the System.IdentityModel.Tokens.Jwt library for .NET, or a third-party library for a different platform.

Be mindful of the following:

  • Make sure to always send an HTTP 202 Accepted status code as part of the response to the change notification.
  • Do that before validating the change notification (for example, if you store change notifications in queues for later processing) or after (if you process them on the fly), even if validation failed.
  • Accepting a change notification prevents unnecessary delivery retries and it also prevents any potential rogue actors from finding out if they passed or failed validation. You can always choose to ignore an invalid change notification after you have accepted it.

In particular, perform validation on every JWT token in the validationTokens collection. If any tokens fail, consider the change notification suspicious and investigate further.

Use the following steps to validate tokens and apps that generate tokens:

  1. Validate that the token has not expired.

  2. Validate the token has not been tampered with and was issued by the expected authority, Microsoft Azure Active Directory:

    • Obtain the signing keys from the common configuration endpoint: This configuration is cached by your app for a period of time. Be aware that the configuration is updated frequently as signing keys are rotated daily.
    • Verify the signature of the JWT token using those keys.

    Do not accept tokens issued by any other authority.

  3. Validate that the token was issued for your app that is subscribing to change notifications.

    The following steps are part of standard validation logic in JWT token libraries and can typically be executed as a single function call.

    • Validate the "audience" in the token matches your app ID.
    • If you have more than one app receiving change notifications, make sure to check for multiple IDs.
  4. Critical: Validate that the app that generated the token represents the Microsoft Graph change notification publisher.

    • Check that the appid property in the token matches the expected value of 0bf30f3b-4a52-48df-9a82-234910c4a086.
    • This ensures that change notifications are not sent by a different app that is not Microsoft Graph.

Example JWT token

The following is an example of the properties included in the JWT token that are needed for validation.

  // aud is your app's id 
  "aud": "8e460676-ae3f-4b1e-8790-ee0fb5d6148f",                           
  "iss": "",
  "iat": 1565046813,
  "nbf": 1565046813,
  // Expiration date 
  "exp": 1565075913,                                                        
  "aio": "42FgYKhZ+uOZrHa7p+7tfruauq1HAA==",
  // appid represents the notification publisher and must always be the same value of 0bf30f3b-4a52-48df-9a82-234910c4a086 
  "appid": "0bf30f3b-4a52-48df-9a82-234910c4a086",                          
  "appidacr": "2",
  "idp": "",
  "tid": "84bd8158-6d4d-4958-8b9f-9d6445542f95",
  "uti": "-KoJHevhgEGnN4kwuixpAA",
  "ver": "1.0"

Example: Verifying validation tokens

// add Microsoft.IdentityModel.Protocols.OpenIdConnect and System.IdentityModel.Tokens.Jwt nuget packages to your project
public async Task<bool> ValidateToken(string token, string tenantId, IEnumerable<string> appIds)
    var configurationManager = new ConfigurationManager<OpenIdConnectConfiguration>("", new OpenIdConnectConfigurationRetriever());
    var openIdConfig = await configurationManager.GetConfigurationAsync();
    var handler = new JwtSecurityTokenHandler();
	handler.ValidateToken(token, new TokenValidationParameters
	    ValidateIssuer = true,
	    ValidateAudience = true,
	    ValidateIssuerSigningKey = true,
	    ValidateLifetime = true,
	    ValidIssuer = $"{tenantId}/",
	    ValidAudiences = appIds,
	    IssuerSigningKeys = openIdConfig.SigningKeys
	}, out _);
	return true;
    catch (Exception ex)
	return false;
private boolean IsValidationTokenValid(String[] appIds, String tenantId, String serializedToken) {
	try {
	    JwkKeyResolver jwksResolver = new JwkKeyResolver();
	    Jws<Claims> token = Jwts.parserBuilder()
	    Claims body = token.getBody();
	    String audience = body.getAudience();
	    boolean isAudienceValid = false;
	    for(String appId : appIds) {
		isAudienceValid = isAudienceValid || appId.equals(audience);
	    boolean isTenantValid = body.getIssuer().endsWith(tenantId + "/");
	    return isAudienceValid  && isTenantValid; //nbf,exp and signature are already validated by library
	} catch (Exception e) {
	    LOGGER.error("could not validate token");
	    return false;
import jwt from 'jsonwebtoken';
import jkwsClient from 'jwks-rsa';

const client = jkwsClient({
  jwksUri: ''

export function getKey(header, callback) {
  client.getSigningKey(header.kid, (err, key) => {
    var signingKey = key.publicKey || key.rsaPublicKey;
    callback(null, signingKey);

export function isTokenValid(token, appId, tenantId) {
  return new Promise((resolve) => {
    const options = {
      audience: [appId],
      issuer: [`${tenantId}/`]
    jwt.verify(token, getKey, options, (err) => {
      if (err) {
        // eslint-disable-next-line no-console
      } else {

For the Java sample to work, you will also need to implement the JwkKeyResolver.

package com.example.restservice;

import com.auth0.jwk.JwkProvider;
import com.auth0.jwk.UrlJwkProvider;
import com.auth0.jwk.Jwk;
import io.jsonwebtoken.Claims;
import io.jsonwebtoken.JwsHeader;
import io.jsonwebtoken.SigningKeyResolverAdapter;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

public class JwkKeyResolver extends SigningKeyResolverAdapter {
    private JwkProvider keyStore;
    private final Logger LOGGER = LoggerFactory.getLogger(this.getClass());
    public JwkKeyResolver() throws, {
        this.keyStore = new UrlJwkProvider((new URI("").toURL()));
    public Key resolveSigningKey(JwsHeader jwsHeader, Claims claims) {
        try {
            String keyId = jwsHeader.getKeyId();
            Jwk pub = keyStore.get(keyId);
            return pub.getPublicKey();
        } catch (Exception e) {
            return null;

Decrypting resource data from change notifications

The resourceData property of a change notification includes only the basic ID and type information of a resource instance. The encryptedData property contains the full resource data, encrypted by Microsoft Graph using the public key provided in the subscription. The property also contains values required for verification and decryption. This is done to increase the security of customer data accessed via change notifications. It is your responsibility to secure the private key to ensure that customer data cannot be decrypted by a third party, even if they manage to intercept the original change notifications.

In this section:

Managing encryption keys

  1. Obtain a certificate with a pair of asymmetric keys.

    • You can self-sign the certificate, since Microsoft Graph does not verify the certificate issuer, and uses the public key for only encryption.

    • Use Azure Key Vault as the solution to create, rotate, and securely manage certificates. Make sure the keys satisfy the following criteria:

      • The key must be of type RSA
      • The key size must be between 2048 and 4096 bits
  2. Export the certificate in base64-encoded X.509 format, and include only the public key.

  3. When creating a subscription:

    • Provide the certificate in the encryptionCertificate property, using the base64-encoded content that the certificate was exported in.

    • Provide your own identifier in the encryptionCertificateId property.

      This identifier allows you to match your certificates to the change notifications you receive, and to retrieve certificates from your certificate store. The identifier can be up to 128 characters.

  4. Manage the private key securely, so that your change notification processing code can access the private key to decrypt resource data.

Rotating keys

To minimize the risk of a private key becoming compromised, periodically change your asymmetric keys. Follow these steps to introduce a new pair of keys:

  1. Obtain a new certificate with a new pair of asymmetric keys. Use it for all new subscriptions being created.

  2. Update existing subscriptions with the new certificate key.

    • Do this as part of regular subscription renewal.
    • Or, enumerate all subscriptions and provide the key. Use the PATCH operation on the subscription and update the encryptionCertificate and encryptionCertificateId properties.
  3. Keep in mind the following:

    • For a period of time, the old certificate may still be used for encryption. Your app must have access to both old and new certificates to be able to decrypt content.
    • Use the encryptionCertificateId property in each change notification to identify the correct key to use.
    • Discard of the old certificate only when you have seen no recent change notifications referencing it.

Decrypting resource data

To optimize performance, Microsoft Graph uses a two-step encryption process:

  • It generates a single use symmetric key, and uses it to encrypt resource data.
  • It uses the public asymmetric key (that you provided when subscribing) to encrypt the symmetric key and includes it in each change notification of that subscription.

Always assume that the symmetric key is different for each item in the change notification.

To decrypt resource data, your app should perform the reverse steps, using the properties under encryptedContent in each change notification:

  1. Use the encryptionCertificateId property to identify the certificate to use.

  2. Initialize an RSA cryptographic component (such as the .NET RSACryptoServiceProvider) with the private key.

  3. Decrypt the symmetric key delivered in the dataKey property of each item in the change notification.

    Use Optimal Asymmetric Encryption Padding (OAEP) for the decryption algorithm.

  4. Use the symmetric key to calculate the HMAC-SHA256 signature of the value in data.

    Compare it to the value in dataSignature. If they do not match, assume the payload has been tampered with and do not decrypt it.

  5. Use the symmetric key with an Advanced Encryption Standard (AES) (such as the .NET AesCryptoServiceProvider) to decrypt the content in data.

    • Use the following decryption parameters for the AES algorithm:

      • Padding: PKCS7
      • Cipher mode: CBC
    • Set the "initialization vector" by copying the first 16 bytes of the symmetric key used for decryption.

  6. The decrypted value is a JSON string that represents the resource instance in the change notification.

Example: decrypting a notification with encrypted resource data

The following is an example change notification that includes encrypted property values of a chatMessage instance in a channel message. The instance is specified by the value.

	"value": [
			"subscriptionId": "76222963-cc7b-42d2-882d-8aaa69cb2ba3",
			"changeType": "created",
			// Other properties typical in a resource change notification
			"resource": "teams('d29828b8-c04d-4e2a-b2f6-07da6982f0f0')/channels('')/messages('1565045424600')/replies('1565047490246')",
			"resourceData": {
				"id": "1565293727947",
				"@odata.type": "#Microsoft.Graph.ChatMessage",
				"": "teams('88cbc8fc-164b-44f0-b6a6-b59b4a1559d3')/channels('19:8d9da062ec7647d4bb1976126e788b47@thread.tacv2')/messages('1565293727947')/replies('1565293727947')"
			"encryptedContent": {
				"data": "{encrypted data that produces a full resource}",
        "dataSignature": "<HMAC-SHA256 hash>",
				"dataKey": "{encrypted symmetric key from Microsoft Graph}",
				"encryptionCertificateId": "MySelfSignedCert/DDC9651A-D7BC-4D74-86BC-A8923584B0AB",
				"encryptionCertificateThumbprint": "07293748CC064953A3052FB978C735FB89E61C3D"
	"validationTokens": [

Note: for a full description of the data sent when change notifications are delivered, see changeNotificationCollection.

This section contains some useful code snippets that use C# and .NET for each stage of decryption.

Decrypt the symmetric key

// Initialize with the private key that matches the encryptionCertificateId.
RSACryptoServiceProvider rsaProvider = ...;        
byte[] encryptedSymmetricKey = Convert.FromBase64String(<value from dataKey property>);

// Decrypt using OAEP padding.
byte[] decryptedSymmetricKey = rsaProvider.Decrypt(encryptedSymmetricKey, fOAEP: true);

// Can now use decryptedSymmetricKey with the AES algorithm.
String storename = ""; //name/path of the jks store
String storepass = ""; //password used to open the jks store
String alias = ""; //alias of the certificate when store in the jks store, should be passed as encryptionCertificateId when subscribing and retrieved from the notification
KeyStore ks = KeyStore.getInstance("JKS");
ks.load(new FileInputStream(storename), storepass.toCharArray());
Key asymmetricKey = ks.getKey(alias, storepass.toCharArray());
byte[] encryptedSymetricKey = Base64.decodeBase64("<value from dataKey property>");
Cipher cipher = Cipher.getInstance("RSA/ECB/OAEPWithSHA1AndMGF1Padding");
cipher.init(Cipher.DECRYPT_MODE, asymmetricKey);
byte[] decryptedSymmetricKey = cipher.doFinal(encryptedSymetricKey);
// Can now use decryptedSymmetricKey with the AES algorithm.
const base64encodedKey = 'base 64 encoded dataKey value';
const asymetricPrivateKey = 'pem encoded private key';
const decodedKey = Buffer.from(base64encodedKey, 'base64');
const decryptedSymetricKey = crypto.privateDecrypt(asymetricPrivateKey, decodedKey);
// Can now use decryptedSymmetricKey with the AES algorithm.

Compare data signature using HMAC-SHA256

byte[] decryptedSymmetricKey = <the aes key decrypted in the previous step>;
byte[] encryptedPayload = <the value from the data property, still encrypted>;
byte[] expectedSignature = <the value from the dataSignature property>;
byte[] actualSignature;

using (HMACSHA256 hmac = new HMACSHA256(decryptedSymmetricKey))
    actualSignature = hmac.ComputeHash(encryptedPayload);
if (actualSignature.SequenceEqual(expectedSignature))
    // Continue with decryption of the encryptedPayload.
    // Do not attempt to decrypt encryptedPayload. Assume notification payload has been tampered with and investigate.
byte[] decryptedSymmetricKey = "<the aes key decrypted in the previous step>";
byte[] decodedEncryptedData = Base64.decodeBase64("data property from encryptedContent object");
Mac mac = Mac.getInstance("HMACSHA256");
SecretKey skey = new SecretKeySpec(decryptedSymmetricKey, "HMACSHA256");
byte[] hashedData = mac.doFinal(decodedEncryptedData);
String encodedHashedData = new String(Base64.encodeBase64(hashedData));
if (comparisonSignature.equals(encodedHashedData))
    // Continue with decryption of the encryptedPayload.
    // Do not attempt to decrypt encryptedPayload. Assume notification payload has been tampered with and investigate.
const decryptedSymetricKey = []; //Buffer provided by previous step
const base64encodedSignature = 'base64 encodded value from the dataSignature property';
const hmac = crypto.createHmac('sha256', decryptedSymetricKey);
hmac.write(base64encodedPayload, 'base64');
if(base64encodedSignature === hmac.digest('base64'))
    // Continue with decryption of the encryptedPayload.
    // Do not attempt to decrypt encryptedPayload. Assume notification payload has been tampered with and investigate.

Decrypt the resource data content

AesCryptoServiceProvider aesProvider = new AesCryptoServiceProvider();
aesProvider.Key = decryptedSymmetricKey;
aesProvider.Padding = PaddingMode.PKCS7;
aesProvider.Mode = CipherMode.CBC;

// Obtain the intialization vector from the symmetric key itself.
int vectorSize = 16;
byte[] iv = new byte[vectorSize];
Array.Copy(decryptedSymmetricKey, iv, vectorSize);
aesProvider.IV = iv;

byte[] encryptedPayload = Convert.FromBase64String(<value from dataKey property>);

string decryptedResourceData;
// Decrypt the resource data content.
using (var decryptor = aesProvider.CreateDecryptor())
  using (MemoryStream msDecrypt = new MemoryStream(encryptedPayload))
      using (CryptoStream csDecrypt = new CryptoStream(msDecrypt, decryptor, CryptoStreamMode.Read))
          using (StreamReader srDecrypt = new StreamReader(csDecrypt))
              decryptedResourceData = srDecrypt.ReadToEnd();

// decryptedResourceData now contains a JSON string that represents the resource.
SecretKey skey = new SecretKeySpec(decryptedSymmetricKey, "AES");
IvParameterSpec ivspec = new IvParameterSpec(Arrays.copyOf(decryptedSymmetricKey, 16));
Cipher cipher = Cipher.getInstance("AES/CBC/PKCS5PADDING");
cipher.init(Cipher.DECRYPT_MODE, skey, ivspec);
String decryptedResourceData = new String(cipher.doFinal(Base64.decodeBase64(encryptedData)));
const base64encodedPayload = 'base64 encoded value from data property';
const decryptedSymetricKey = []; //Buffer provided by previous step
const iv = Buffer.alloc(16, 0);
decryptedSymetricKey.copy(iv, 0, 0, 16);
const decipher = crypto.createDecipheriv('aes-256-cbc', decryptedSymetricKey, iv);
let decryptedPayload = decipher.update(base64encodedPayload, 'base64', 'utf8');
decryptedPayload +='utf8');

See also