Répertorier les objets changeItemBase

Espace de noms: microsoft.graph

Obtenez la liste des objets changeItemBase et de leurs propriétés. L’API retourne à la fois Microsoft Entra annonces de modification et les mises en production.

Cette API est disponible dans les déploiements de cloud national suivants.

Autorisations

Choisissez l’autorisation ou les autorisations marquées comme moins privilégiées pour cette API. Utilisez une autorisation ou des autorisations privilégiées plus élevées uniquement si votre application en a besoin. Pour plus d’informations sur les autorisations déléguées et d’application, consultez Types d’autorisations. Pour en savoir plus sur ces autorisations, consultez les informations de référence sur les autorisations.

Tout utilisateur peut appeler ces API, il n’y a aucune exigence de rôle d’administrateur.

Requête HTTP

GET /identity/productChanges

Paramètres facultatifs de la requête

Cette méthode prend en charge les $countparamètres de requête , $filter (eq, ne, instartswith, ), $orderby, $search, $top (la taille de page par défaut est de 10 éléments, le maximum est de 250 éléments) $select et $skip les paramètres de requête OData pour vous aider à personnaliser la réponse.

En-têtes de demande

Corps de la demande

N’indiquez pas le corps de la demande pour cette méthode.

Réponse

Si elle réussit, cette méthode renvoie un 200 OK code de réponse et une collection d’objets changeItemBase dans le corps de la réponse.

Exemples

Demande

L’exemple suivant illustre une demande.

GET https://graph.microsoft.com/beta/identity/productChanges

// Code snippets are only available for the latest version. Current version is 5.x

// To initialize your graphClient, see https://zcusa.951200.xyz/en-us/graph/sdks/create-client?from=snippets&tabs=csharp
var result = await graphClient.Identity.ProductChanges.GetAsync();

mgc-beta identity product-changes list

// Code snippets are only available for the latest major version. Current major version is $v0.*

// Dependencies
import (
	  "context"
	  msgraphsdk "github.com/microsoftgraph/msgraph-beta-sdk-go"
	  //other-imports
)


// To initialize your graphClient, see https://zcusa.951200.xyz/en-us/graph/sdks/create-client?from=snippets&tabs=go
productChanges, err := graphClient.Identity().ProductChanges().Get(context.Background(), nil)

// Code snippets are only available for the latest version. Current version is 6.x

GraphServiceClient graphClient = new GraphServiceClient(requestAdapter);

ChangeItemBaseCollectionResponse result = graphClient.identity().productChanges().get();

const options = {
	authProvider,
};

const client = Client.init(options);

let productChanges = await client.api('/identity/productChanges')
	.version('beta')
	.get();

<?php
use Microsoft\Graph\Beta\GraphServiceClient;


$graphServiceClient = new GraphServiceClient($tokenRequestContext, $scopes);


$result = $graphServiceClient->identity()->productChanges()->get()->wait();

# Code snippets are only available for the latest version. Current version is 1.x
from msgraph_beta import GraphServiceClient
# To initialize your graph_client, see https://zcusa.951200.xyz/en-us/graph/sdks/create-client?from=snippets&tabs=python

result = await graph_client.identity.product_changes.get()

Réponse

L’exemple suivant illustre la réponse.

Remarque : l’objet de réponse affiché ci-après peut être raccourci pour plus de lisibilité.

HTTP/1.1 200 OK
Content-Type: application/json

{
    "@odata.context": "https://graph.microsoft.com/beta/$metadata#identity/productChanges",
    "@odata.nextLink": "https://graph.microsoft.com/beta/identity/productChanges?$skip=10",
    "@microsoft.graph.tips": "Use $select to choose only the properties your app needs, as this can lead to performance improvements. For example: GET identity/productChanges?$select=changeItemService,description",
    "value": [
        {
            "@odata.type": "#microsoft.graph.announcement",
            "id": "01ec4ab4-e288-4e1c-8f8c-d5b0bc68b866",
            "changeItemService": "msGraph",
            "tags": [
                "Identity Security"
            ],
            "systemTags": [],
            "documentationUrls": [
                "https://techcommunity.microsoft.com/t5/microsoft-entra-blog/important-update-azure-ad-graph-api-retirement/ba-p/4090534"
            ],
            "shortDescription": "Latest update on migrating your applications from Azure AD Graph to Microsoft Graph",
            "title": "Migrate your apps to Microsoft Graph API",
            "description": "In June of 2023, we shared an update on completion of a three-year notice period for the deprecation of the Azure AD Graph API service. The service is now in the retirement cycle and retirement (shut down) will be done with incremental stages. In the first stage of this retirement cycle, applications that are created after June 30, 2024, will receive an error (HTTP 403) for any requests to Azure AD Graph APIs ( https://graph.windows.net ). \n \n We understand that some apps may not have fully completed migration to Microsoft Graph. We are providing an optional configuration that will allow an application created after June 30, 2024, to resume use of Azure AD Graph APIs through June 2025. If you develop or distribute software that requires applications to be created as part of the installation or setup, and these applications will need to access Azure AD Graph APIs, you must prepare now to avoid interruption. \n \n We have recently begun rollout of Microsoft Entra recommendations to help monitor the status of your tenant, plus provide information about applications and service principals that are using Azure AD Graph APIs in your tenant. These new recommendations provide information to support your efforts to migrate the impacted applications and service principals to Microsoft Graph. \n \n For more information on Azure AD Graph retirement, the new recommendations for Azure AD Graph, and configuring applications created after June 30, 2024, for an extension of Azure AD Graph APIs, please click 'Learn more' below.",
            "announcementDateTime": "2020-06-23T00:00:00Z",
            "targetDateTime": "2024-06-30T00:00:00Z",
            "impactLink": null,
            "changeType": "retirement",
            "isCustomerActionRequired": true
        },
        {
            "@odata.type": "#microsoft.graph.roadmap",
            "id": "0d17a065-f34c-4954-9a0a-2f9b45c5c166",
            "changeItemService": "entitlementManagement",
            "tags": [
                ""
            ],
            "systemTags": [],
            "documentationUrls": [
                "https://zcusa.951200.xyz/en-us/entra/identity/role-based-access-control/permissions-reference#organizational-branding-administrator"
            ],
            "shortDescription": "",
            "title": "Organizational Branding role for Entra ID Company Branding",
            "description": "The new Organizational Branding Administrator privileges are limited to branding, allowing you to adhere to the principle of least privilege by eliminating the need for the Global Administrator role to configure branding.",
            "changeItemState": "available",
            "deliveryStage": "ga",
            "category": "accessControl",
            "publishedDateTime": "2024-05-06T07:00:00Z",
            "gotoLink": null
        }
    ]
}