Skip to content

[o365] Improve permissions documentation #15228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 4 commits into from
Sep 9, 2025
Merged

[o365] Improve permissions documentation #15228

merged 4 commits into from
Sep 9, 2025

Conversation

@chrisberkhout
Copy link
Contributor

@chrisberkhout chrisberkhout commented Sep 8, 2025 •
edited
Loading

Proposed commit message

[o365] Improve permissions documentation

To mention the non-own tenant case and include a troubleshooting tip.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

@chrisberkhout chrisberkhout self-assigned this Sep 8, 2025
@chrisberkhout chrisberkhout requested a review from a team as a code owner September 8, 2025 15:40
@chrisberkhout chrisberkhout added enhancement New feature or request Integration:o365 Microsoft Office 365 Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels Sep 8, 2025
@elasticmachine
Copy link

elasticmachine commented Sep 8, 2025

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@chrisberkhout chrisberkhout force-pushed the o365-doc-consent-troubleshooting branch from 8c7d84c to 3812d62 Compare September 8, 2025 15:42
@andrewkroh andrewkroh added the documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. label Sep 8, 2025
efd6
efd6 reviewed Sep 9, 2025
View reviewed changes
@chrisberkhout chrisberkhout requested a review from efd6 September 9, 2025 06:16
@chrisberkhout chrisberkhout enabled auto-merge (squash) September 9, 2025 06:20
@elastic-vault-github-plugin-prod
Copy link

elastic-vault-github-plugin-prod bot commented Sep 9, 2025

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@chrisberkhout chrisberkhout merged commit 761d622 into elastic:main Sep 9, 2025
7 checks passed
@elasticmachine
Copy link

elasticmachine commented Sep 9, 2025

💚 Build Succeeded

History

cc @chrisberkhout

@elastic-sonarqube
Copy link

elastic-sonarqube bot commented Sep 9, 2025

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

@elastic-vault-github-plugin-prod
Copy link

elastic-vault-github-plugin-prod bot commented Sep 9, 2025

Package o365 - 2.27.0 containing this change is available at https://epr.elastic.co/package/o365/2.27.0/

tehbooom pushed a commit to tehbooom/integrations that referenced this pull request Nov 19, 2025
@chrisberkhout @efd6
[o365] Improve permissions documentation (elastic#15228)
9f8fff0 
To mention the non-own tenant case and include a troubleshooting tip.

---------

Co-authored-by: Dan Kortschak <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@efd6 efd6 efd6 approved these changes

Assignees

@chrisberkhout chrisberkhout

Labels

documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request Integration:o365 Microsoft Office 365 Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@chrisberkhout @elasticmachine @efd6 @andrewkroh