Delete the default organizational branding object. To delete the organizationalBranding object, all images (Stream types) must first be removed from the object.
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
Permission type
Least privileged permissions
Higher privileged permissions
Delegated (work or school account)
OrganizationalBranding.ReadWrite.All
Organization.ReadWrite.All
Delegated (personal Microsoft account)
Not supported.
Not supported.
Application
OrganizationalBranding.ReadWrite.All
Not available.
For delegated scenarios, only users with the Oragnizational Branding AdministratorMicrosoft Entra role can fully manage the organization's branding.
// Code snippets are only available for the latest version. Current version is 5.x
// Dependencies
using Microsoft.Graph.Organization.Item.Branding;
var requestBody = new BrandingDeleteRequestBody
{
AdditionalData = new Dictionary<string, object>
{
{
"id" , "0"
},
},
};
// To initialize your graphClient, see https://learn.microsoft.com/en-us/graph/sdks/create-client?from=snippets&tabs=csharp
await graphClient.Organization["{organization-id}"].Branding.DeleteAsync(requestBody);
// Code snippets are only available for the latest version. Current version is 6.x
GraphServiceClient graphClient = new GraphServiceClient(requestAdapter);
com.microsoft.graph.organization.item.branding.BrandingDeleteRequestBody brandingDeleteRequestBody = new com.microsoft.graph.organization.item.branding.BrandingDeleteRequestBody();
HashMap<String, Object> additionalData = new HashMap<String, Object>();
additionalData.put("id", "0");
brandingDeleteRequestBody.setAdditionalData(additionalData);
graphClient.organization().byOrganizationId("{organization-id}").branding().delete(brandingDeleteRequestBody);
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.