You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The URL of the endpoint that will receive the lifecycle notifications. This URL must use the HTTPS protocol.
--notificationUrlAppId [notificationUrlAppId]
The app ID that the subscription service can use to generate the validation token. The value allows the client to validate the authenticity of the notification received.
--latestTLSVersion [latestTLSVersion]
The latest version of TLS that the notification endpoint supports. Allowed values are v1_0, v1_1, v1_2, v1_3. Default is v1_2.
--includeResourceData
When set, the change notifications will include the changed resource data.
--encryptionCertificate [encryptionCertificate]
A base64-encoded representation of a certificate with a public key used to encrypt resource data in change notifications. Required when using includeResourceData.
A custom app-provided identifier to help identify the certificate needed to decrypt resource data.
Remarks
(instead of note, use info admonition)
Note
For subscribers whose notification endpoint supports a version lower than the currently recommended version (TLS 1.2), specifying this property by a set timeline allows them to temporarily use their deprecated version of TLS before completing their upgrade to TLS 1.2. For these subscribers, not setting this property per the timeline would result in subscription operations failing.
The
POST v1.0/subscriptions
endpoint supports more options than we currently have. So the idea is to include these as new options.Options
--lifecycleNotificationUrl [lifecycleNotificationUrl]
--notificationUrlAppId [notificationUrlAppId]
--latestTLSVersion [latestTLSVersion]
v1_0
,v1_1
,v1_2
,v1_3
. Default isv1_2
.--includeResourceData
--encryptionCertificate [encryptionCertificate]
includeResourceData
.--encryptionCertificateId [encryptionCertificateId]
Remarks
(instead of note, use info admonition)
Note
For subscribers whose notification endpoint supports a version lower than the currently recommended version (TLS 1.2), specifying this property by a set timeline allows them to temporarily use their deprecated version of TLS before completing their upgrade to TLS 1.2. For these subscribers, not setting this property per the timeline would result in subscription operations failing.
Additional options
More info can be found here: https://learn.microsoft.com/graph/api/resources/subscription?view=graph-rest-1.0#properties
The text was updated successfully, but these errors were encountered: