Merge pull request #25212 from microsoftgraph/main

Lauragra · web-flow · commit ba5128be958f · 2024-09-19T18:24:01.000-07:00
Merge to publish.
diff --git a/api-reference/beta/resources/claimsmappingpolicy.md b/api-reference/beta/resources/claimsmappingpolicy.md
@@ -23,6 +23,8 @@ The number of claims and transformations that can be added to a claims-mapping p
 
 For more scenario and configuration details, see [Claims mapping policy type](/azure/active-directory/develop/reference-claims-mapping-policy-type) and [How to: Customize claims emitted in tokens for a specific app in a tenant](/azure/active-directory/develop/active-directory-claims-mapping#claims-mapping-policy-properties).
 
+Additionally, visit [Claims customization using a policy](/entra/identity-platform/reference-claims-customization) to learn the difference between this policy and the [custom claims policy](../resources/customclaimspolicy.md).
+
 Inherits from [stsPolicy](stsPolicy.md).
 
 ## Methods
diff --git a/api-reference/beta/resources/customclaimspolicy.md b/api-reference/beta/resources/customclaimspolicy.md
@@ -14,7 +14,9 @@ Namespace: microsoft.graph
 
 [!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
 
-Represents a claims policy that allows application admins to customize the claims emitted in tokens affected by this policy.
+Represents a claims policy that allows application admins to customize the claims emitted in tokens affected by this policy. Learn more about this policy in the following articles:
+- [Customize claims using the custom claims policy (preview)](/entra/identity-platform/claims-customization-custom-claims-policy)
+- [Claims customization using a policy](/entra/identity-platform/reference-claims-customization) to learn the difference between this policy and the [claims mapping policy](../resources/claimsmappingpolicy.md)
 
 Inherits from [entity](../resources/entity.md).
 
diff --git a/api-reference/beta/resources/invalidlicensealertconfiguration.md b/api-reference/beta/resources/invalidlicensealertconfiguration.md
@@ -18,6 +18,12 @@ Represents an alert configuration that's triggered if the tenant doesn't have a
 
 Inherits from [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md).
 
+
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/invalidlicensealertincident.md b/api-reference/beta/resources/invalidlicensealertincident.md
@@ -18,6 +18,11 @@ Represents the details of an alert incident that is triggered if the current ten
 
 Inherits from [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/nomfaonroleactivationalertconfiguration.md b/api-reference/beta/resources/nomfaonroleactivationalertconfiguration.md
@@ -18,6 +18,11 @@ Represents an alert configuration that is triggered if roles don't require multi
 
 Inherits from [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/nomfaonroleactivationalertincident.md b/api-reference/beta/resources/nomfaonroleactivationalertincident.md
@@ -18,6 +18,11 @@ Represents the details of an alert incident that is triggered if roles don't req
 
 Inherits from [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/redundantassignmentalertconfiguration.md b/api-reference/beta/resources/redundantassignmentalertconfiguration.md
@@ -18,6 +18,11 @@ Represents an alert configuration that is triggered if a user goes over a specif
 
 Inherits from [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/redundantassignmentalertincident.md b/api-reference/beta/resources/redundantassignmentalertincident.md
@@ -20,6 +20,11 @@ The threshold that triggers this incident when it's reached is defined in the [r
 
 Inherits from [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/reflectcheckinresponse.md b/api-reference/beta/resources/reflectcheckinresponse.md
@@ -33,8 +33,8 @@ Inherits from [entity](../resources/entity.md).
 |creatorId|String|ID of the user who created the Reflect check-in.|
 |isClosed|Boolean|Indicates whether the Reflect check-in is closed (`true`) or open (`false`).|
 |responderId|String|ID of the user who responded to the Reflect check-in.|
-|responseEmotion|responseEmotionType|Represents the pleasantness level of the response that indicates how pleasant the responder felt. The possible values are: `none`, `confident`, `excited`, `happy`, `motivated`, `peaceful`, `ambitious`, `cheerful`, `comfortable`, `creative`, `determined`, `energized`, `focused`, `fulfilled`, `grateful`, `included`, `inspired`, `optimistic`, `proud`, `successful`, `valuable`, `annoyed`, `bored`, `calm`, `confused`, `glad`, `content`, `pensive`, `reserved`, `restless`, `shocked`, `tired`, `angry`, `depressed`, `exhausted`, `lonely`, `nervous`, `anxious`, `apathetic`, `concerned`, `disappointed`, `frightened`, `frustrated`, `hopeless`, `hurt`, `jealous`, `miserable`, `overwhelmed`, `skeptical`, `stressed`, `stuck`, `worthless`, `awed`, `ashamed`, `curious`, `sensitive`, `sad`, `unknownFutureValue`.|
-|responseFeedback|responseFeedbackType|Represents the exact emotion name that the responder felt during the Reflect check-in response. The possible values are: `none`, `notDetected`, `veryUnpleasant`, `unpleasant`, `neutral`, `pleasant`, `veryPleasant`, `unknownFutureValue`.|
+|responseEmotion|responseEmotionType|Represents the exact emotion name that the responder felt during the Reflect check-in response. The possible values are: `none`, `confident`, `excited`, `happy`, `motivated`, `peaceful`, `ambitious`, `cheerful`, `comfortable`, `creative`, `determined`, `energized`, `focused`, `fulfilled`, `grateful`, `included`, `inspired`, `optimistic`, `proud`, `successful`, `valuable`, `annoyed`, `bored`, `calm`, `confused`, `glad`, `content`, `pensive`, `reserved`, `restless`, `shocked`, `tired`, `angry`, `depressed`, `exhausted`, `lonely`, `nervous`, `anxious`, `apathetic`, `concerned`, `disappointed`, `frightened`, `frustrated`, `hopeless`, `hurt`, `jealous`, `miserable`, `overwhelmed`, `skeptical`, `stressed`, `stuck`, `worthless`, `awed`, `ashamed`, `curious`, `sensitive`, `sad`, `unknownFutureValue`.|
+|responseFeedback|responseFeedbackType|Represents the pleasantness level of the response that indicates how pleasant the responder felt. The possible values are: `none`, `notDetected`, `veryUnpleasant`, `unpleasant`, `neutral`, `pleasant`, `veryPleasant`, `unknownFutureValue`.|
 |submitDateTime|DateTimeOffset|Date and time when the response to the Reflect check-in was submitted. The timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`.|
 
 ## Relationships
diff --git a/api-reference/beta/resources/rolesassignedoutsideprivilegedidentitymanagementalertconfiguration.md b/api-reference/beta/resources/rolesassignedoutsideprivilegedidentitymanagementalertconfiguration.md
@@ -18,6 +18,11 @@ Represents an alert configuration that is triggered if Microsoft Entra roles hav
 
 Inherits from [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/rolesassignedoutsideprivilegedidentitymanagementalertincident.md b/api-reference/beta/resources/rolesassignedoutsideprivilegedidentitymanagementalertincident.md
@@ -18,6 +18,11 @@ Represents an alert incident that is triggered if roles have been assigned outsi
 
 Inherits from [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/sequentialactivationrenewalsalertconfiguration.md b/api-reference/beta/resources/sequentialactivationrenewalsalertconfiguration.md
@@ -18,6 +18,11 @@ Represents an alert configuration that is triggered if a user activates the same
 
 Inherits from [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/sequentialactivationrenewalsalertincident.md b/api-reference/beta/resources/sequentialactivationrenewalsalertincident.md
@@ -18,6 +18,11 @@ Represents an alert incident that is triggered if a user activates the same priv
 
 Inherits from [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/stalesigninalertconfiguration.md b/api-reference/beta/resources/stalesigninalertconfiguration.md
@@ -18,6 +18,11 @@ Represents an alert configuration that is triggered if there are accounts in a p
 
 Inherits from [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/stalesigninalertincident.md b/api-reference/beta/resources/stalesigninalertincident.md
@@ -20,6 +20,11 @@ The threshold that triggers this alert when it's reached is defined in the [stal
 
 Inherits from [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/toomanyglobaladminsassignedtotenantalertconfiguration.md b/api-reference/beta/resources/toomanyglobaladminsassignedtotenantalertconfiguration.md
@@ -20,6 +20,11 @@ Triggered if two different criteria are met, and you can configure both of them.
 
 Inherits from [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertConfiguration](../resources/unifiedrolemanagementalertconfiguration.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/resources/toomanyglobaladminsassignedtotenantalertincident.md b/api-reference/beta/resources/toomanyglobaladminsassignedtotenantalertincident.md
@@ -20,6 +20,11 @@ The threshold that triggers this incident when its reached is defined in the [to
 
 Inherits from [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md).
 
+## Methods
+None.
+
+For the list of API operations for managing this resource type, see the [unifiedRoleManagementAlertIncident](../resources/unifiedrolemanagementalertincident.md) resource type.
+
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
diff --git a/api-reference/beta/toc/security/toc.yml b/api-reference/beta/toc/security/toc.yml
@@ -492,10 +492,6 @@ items:
       href: ../../api/security-sensor-getdeploymentaccesskey.md
     - name: Regenerate deployment access key
       href: ../../api/security-sensor-regeneratedeploymentaccesskey.md
-  - name: Complex types
-    items:
-    - name: Identity container
-      href: ../../resources/security-identitycontainer.md
 - name: Information protection
   items:
   - name: Information protection label
diff --git a/api-reference/v1.0/resources/claimsmappingpolicy.md b/api-reference/v1.0/resources/claimsmappingpolicy.md
@@ -21,6 +21,8 @@ The number of claims and transformations that can be added to a claims-mapping p
 
 For more scenario and configuration details, see [Claims mapping policy type](/azure/active-directory/develop/reference-claims-mapping-policy-type) and [How to: Customize claims emitted in tokens for a specific app in a tenant](/azure/active-directory/develop/active-directory-claims-mapping#claims-mapping-policy-properties).
 
+Additionally, visit [Claims customization using a policy](/entra/identity-platform/reference-claims-customization) to learn the difference between this policy and the [custom claims policy](/graph/api/resources/customclaimspolicy).
+
 Inherits from [stsPolicy](stsPolicy.md).
 
 ## Methods
diff --git a/changelog/Manual.NonWorkloadChanges.json b/changelog/Manual.NonWorkloadChanges.json
@@ -1,5 +1,23 @@
 {
   "changelog": [
+    {
+      "ChangeList": [
+        {
+          "Id": "bf84f9b9-7809-48b4-aeeb-4db380be2b4b",
+          "ApiChange": "Resource",
+          "ChangedApiName": "changeNotification",
+          "ChangeType": "Deprecation",
+          "Description": "Authenticating Event Hubs by using shared access signatures (SAS) will be deprecated soon. To subscribe to [Microsoft Graph change notifications via Azure Event Hubs](https://learn.microsoft.com/en-us/graph/change-notifications-delivery-event-hubs), we recommend using Microsoft Entra ID role-based access control (RBAC) instead. Follow the [guidance to migrate to RBAC](https://learn.microsoft.com/en-us/graph/change-notifications-delivery-event-hubs#migrate-an-event-hub-authentication-to-microsoft-entra-id-rbac).",
+          "Target": "changeNotification"
+        }
+      ],
+      "Id": "bf84f9b9-7809-48b4-aeeb-4db380be2b4b",
+      "Cloud": "prd",
+      "Version": "v1.0",
+      "CreatedDateTime": "2024-09-19T00:00:00",
+      "WorkloadArea": "Change notifications",
+      "SubArea": ""
+    },
     {
       "ChangeList": [
         {
@@ -145,4 +163,4 @@
       "SubArea": "Schema extensions"
     }
   ]
-}
+}
diff --git a/concepts/change-notifications-delivery-event-hubs.md b/concepts/change-notifications-delivery-event-hubs.md
@@ -181,9 +181,9 @@ If you're using role-based access control, the **notificationUrl** property look
 
 `EventHub:https://<eventhubnamespace>.servicebus.windows.net/eventhubname/<eventhubname>?tenantId=<domainname>`
 
-- `eventhubnamespace` is the name you give to the Event Hubs namespace. It can be found in the Event Hubs Overview page under Host name.
-- `eventhubname` is the name you give to the event hub. It can be found in the Event Hubs -> Overview -> Event Hubs.
-- `domainname` is the name of your tenant; for example, `contoso.com`. Because this domain is used to access the Azure Event Hubs, it's important that it matches the domain used by the Azure subscription that holds the Azure Event Hubs. To get this information, select the Microsoft Entra ID menu on the Azure portal and check the Overview page. The domain name is displayed under the **Primary domain**.
+- `<eventhubnamespace>` is the name you give to the Event Hubs namespace. It can be found on the Event Hubs Overview page under Host name.
+- `<eventhubname>` is the name you give to the event hub. It can be found in the Event Hubs -> Overview -> Event Hubs.
+- `<domainname>` is the name of your tenant; for example, `contoso.com`. Because this domain is used to access the Azure Event Hubs, it's important that it matches the domain used by the Azure subscription that holds the Azure Event Hubs. To get this information, select the Microsoft Entra ID menu on the Azure portal and check the Overview page. The domain name is displayed under the **Primary domain**.
 
 <!-- End of "Using RBAC tab-->
 
@@ -192,9 +192,9 @@ If you're using role-based access control, the **notificationUrl** property look
 
 If you're using Key Vault, the **notificationUrl** property looks like this: `EventHub:https://<azurekeyvaultname>.vault.azure.net/secrets/<secretname>?tenantId=<domainname>`, with the following values:
 
-- `azurekeyvaultname` - The name you gave to the key vault during creation. It can be found in the DNS name.
-- `secretname` - The name you gave to the secret during creation. It can be found on the Azure Key Vault **Secrets** page.
-- `domainname` - The name of your tenant; for example, `contoso.com`. Because this domain is used to access the Azure Key Vault, it's important that it matches the domain used by the Azure subscription that holds the Azure Key Vault. To get this information, you can go to the overview page of the Azure Key Vault you created and select the subscription. The domain name is displayed under the **Directory** field.
+- `<azurekeyvaultname>` - The name you gave to the key vault during creation. It can be found in the DNS name.
+- `<secretname>` - The name you gave to the secret during creation. It can be found on the Azure Key Vault **Secrets** page.
+- `<domainname>` - The name of your tenant; for example, `contoso.com`. Because this domain is used to access the Azure Key Vault, it's important that it matches the domain used by the Azure subscription that holds the Azure Key Vault. To get this information, you can go to the overview page of the Azure Key Vault you created and select the subscription. The domain name is displayed under the **Directory** field.
 
 <!-- End of "Using Key Vault tab-->
 
diff --git a/concepts/whats-new-overview.md b/concepts/whats-new-overview.md
@@ -18,6 +18,10 @@ For details about previous updates to Microsoft Graph, see [Microsoft Graph what
 
 ## September 2024: New and generally available
 
+### Change notifications
+
+Announced the deprecation of shared access signatures (SAS) for authenticating Event Hubs for [Microsoft Graph change notifications](/graph/change-notifications-delivery-event-hubs). We recommend using Microsoft Entra ID role-based access control (RBAC) instead. Follow the [guidance to migrate to RBAC](/graph/change-notifications-delivery-event-hubs#migrate-an-event-hub-authentication-to-microsoft-entra-id-rbac).
+
 ### Security | Identities
 
 Added the ability to [get](/graph/api/security-healthissue-get), [list](/graph/api/security-identitycontainer-list-healthissues), and [update](/graph/api/security-healthissue-update) Microsoft Defender for Identity [health issues](/graph/api/resources/security-healthissue) that represent potential issues identified within a customer's Defender for Identity configuration.
