Others

How to Find the Publisher ID for Office 365 Management API

Jason MillerJason Miller Oct 22, 2026 870 views

Question details

The user needs to identify the Publisher ID for the Office 365 Management Activity API to successfully configure an integration with a third-party SIEM service.

How to Find the Publisher ID for Office 365 Management API
Product
Microsoft 365
Device & OS
not provided
Scenario
Connecting Microsoft 365 to external security or logging services (such as Logsign SIEM) using Azure API credentials.
Observed behavior
The connection attempt fails with a "Login error" because the Publisher ID field is misunderstood or missing during configuration.
Before you start

Ensure you have global administrator or Azure Active Directory (Microsoft Entra ID) administrator privileges to access and view your Microsoft 365 tenant properties.

Solution 1Recommended

Use the Microsoft 365 Tenant ID as the Publisher ID

For the Office 365 Management Activity API, the term "Publisher ID" actually refers to your Microsoft 365 Tenant ID (or Tenant GUID). You must locate this ID in Azure and input it into your SIEM configuration.

Many third-party services use the term 'Publisher ID' interchangeably with 'Tenant ID' when integrating with Microsoft APIs. Finding your unique Tenant GUID will resolve this credential requirement.

1
Sign in to the Azure Portal

Go to the Microsoft Azure portal (portal.azure.com) or the Microsoft Entra admin center and sign in with your administrator account.

2
Navigate to Microsoft Entra ID

In the left-hand navigation menu, click on 'Microsoft Entra ID' (formerly known as Azure Active Directory).

3
Locate the Tenant ID

On the Overview page, look under the 'Basic information' section. You will see a field labeled 'Tenant ID'. Copy this alphanumeric string.

4
Enter the Publisher ID in your application

Return to your external application (e.g., Logsign SIEM) and paste the copied Tenant ID into the 'Publisher ID' field, then save your configuration and test the connection.

Use the Microsoft 365 Tenant ID as the Publisher ID
Connection tip: Ensure there are no leading or trailing spaces when pasting the Tenant ID into your third-party application, as this can trigger a login error.
Free Microsoft Office alternative

Looking for a Lightweight Office Solution? Try WPS Office

While WPS Office does not manage Microsoft 365 Azure APIs or SIEM integrations, it serves as a powerful, free, and lightweight alternative to Microsoft Office for your daily document creation and editing needs.

  1. 1. Download the software: Visit the official WPS Office website and download the free installer for your operating system.
  2. 2. Install WPS Office: Run the installer and follow the quick on-screen instructions to set up the suite on your computer.
  3. 3. Open existing files: Launch WPS Office and directly open your existing Microsoft Office files without worrying about format compatibility.
Completely free to download and use for basic office tasksHighly compatible with Microsoft Word, Excel, and PowerPoint formatsLightweight installation that runs smoothly on older devicesFamiliar user interface for a seamless transition from Microsoft Office
microsoft office alternative - wps office

Frequently Asked Questions

What is the difference between Application ID and Publisher ID?

The Application ID uniquely identifies the specific app registration you created in Azure AD for your integration. The Publisher ID (or Tenant ID) identifies your entire Microsoft 365 organization. Both are required when authenticating with the Office 365 Management Activity API.

Why am I getting a login error when connecting my SIEM to Office 365?

A login error usually occurs if the Publisher ID (Tenant ID), Application ID, or Client Secret is entered incorrectly. It can also happen if you have not clicked 'Grant admin consent' for the required API permissions in the Azure portal.

Does the Office 365 Management API require a special license?

Yes, to generate and retrieve audit logs via the Office 365 Management Activity API, your organization needs an enterprise subscription (like E3 or E5) that includes Office 365 audit logging capabilities, and audit logging must be turned on in the Microsoft Purview compliance portal.