3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node operation "Get Users By Principal Names" within the "Microsoft 365 Integration" resource is designed to retrieve user information from Microsoft 365 based on a list of principal names (user identifiers such as email addresses or usernames). It is useful in scenarios where you need to fetch detailed user profiles or verify user existence in bulk by providing their principal names.

Practical examples include:

  • Synchronizing user data from Microsoft 365 into another system.
  • Validating a list of users before performing batch operations.
  • Fetching user details for reporting or auditing purposes.

Properties

Name Meaning
Principal Names A JSON array containing one or more principal names (e.g., email addresses) to query.

The property expects a JSON array input, for example:

[
  "user1@example.com",
  "user2@example.com"
]

Output

The output will contain a json field with the retrieved user objects corresponding to each principal name provided. Each user object typically includes user profile details such as display name, email, job title, and other relevant Microsoft 365 user attributes.

If the node supports binary data output, it would generally relate to attachments or files associated with the user, but this operation primarily returns JSON user data.

Dependencies

  • Requires an active connection to Microsoft 365 services with appropriate API permissions to read user information.
  • Needs an API authentication token or credential configured in n8n to authorize requests against Microsoft 365 Graph API or equivalent service.

Troubleshooting

  • Empty or null results: Ensure that the principal names provided are valid and exist in the Microsoft 365 tenant.
  • Authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions to read user data.
  • Invalid JSON input: The "Principal Names" property must be a valid JSON array; malformed JSON will cause parsing errors.
  • Rate limiting or throttling: Microsoft 365 APIs may limit request rates; consider adding retry logic or reducing batch sizes if encountering rate limit errors.

Links and References

Discussion