Skip to content

EWS Extension Documentation Improvements - #46200

Open
nbensalm-palo wants to merge 12 commits into
masterfrom
ews-extension-exo-readme-permissions-update
Open

nbensalm-palo wants to merge 12 commits into
masterfrom
ews-extension-exo-readme-permissions-update

Conversation

@nbensalm-palo

@nbensalm-palo nbensalm-palo commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Status

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

https://jira-dc.paloaltonetworks.com/browse/XSUP-77394
https://jira-dc.paloaltonetworks.com/browse/CRTX-283758

Description

Documentation improvements for EWS Extension Online Powershell v3.
Updated the guidance for granting the application Exchange Online permissions to clarify that one of two options is sufficient, and added a PowerShell-based procedure for adding the service principal.

Must have

  • Tests
  • Documentation

@nbensalm-palo nbensalm-palo added ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. labels Oct 8, 2026
@content-bot

Copy link
Copy Markdown
Contributor

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @marketplace-ai-reviewer start review - Initiate a full AI code review
  • @marketplace-ai-reviewer re-review - Incremental review for new commits

@marketplace-ai-reviewer marketplace-ai-reviewer removed the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Oct 8, 2026
@marketplace-ai-reviewer

Copy link
Copy Markdown
Contributor

🤖 Analysis started. Please wait for results...

@marketplace-ai-reviewer

Copy link
Copy Markdown
Contributor
🤖 AI Review Disclaimer

This review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause.

@marketplace-ai-reviewer marketplace-ai-reviewer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution! I've reviewed the changes and have a few minor adjustments to suggest.

Please ensure the pack metadata includes the mandatory created key and the vendor name in the keywords. Also, since this PR only updates documentation, the release notes should be simplified to use the standard documentation template.

Let me know if you have any questions!

Additionally, please address the following file-level notes:

  • Packs/MicrosoftExchangeOnline/pack_metadata.json: - Missing mandatory key created.
  • Vendor name missing from keywords.

@nbensalm-palo please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.

Comment thread Packs/MicrosoftExchangeOnline/Integrations/EwsExtensionEXOPowershellV3/README.md Outdated
Comment thread Packs/MicrosoftExchangeOnline/ReleaseNotes/1_10_12.md Outdated
@content-bot

This comment has been minimized.

…eadme-permissions-update

# Conflicts:
#	Packs/MicrosoftExchangeOnline/ReleaseNotes/1_10_12.md
#	Packs/MicrosoftExchangeOnline/pack_metadata.json
@nbensalm-palo
nbensalm-palo marked this pull request as ready for review October 20, 2026 20:38
@nbensalm-palo

Copy link
Copy Markdown
Contributor Author

Hey @richardbluestone ,
I'll be happy for a doc review regarding this PR.

@content-bot

This comment has been minimized.

@JuliaH-TW JuliaH-TW left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nbensalm-palo
No documentation updates needed.

…eadme-permissions-update

# Conflicts:
#	Packs/MicrosoftExchangeOnline/ReleaseNotes/1_10_14.md
@content-bot

This comment has been minimized.

Comment thread Packs/MicrosoftExchangeOnline/Integrations/EwsExtensionEXOPowershellV3/README.md Outdated
@content-bot

Copy link
Copy Markdown
Contributor

Validate summary
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.

Verdict: PR can be force merged from validate perspective? ✅

@content-bot

Copy link
Copy Markdown
Contributor

🔍 AI Triage Report Available

An automated triage report has been generated for this pipeline.

Status: success
Report ID: c466f48b4c7b39ec

📋 Triage Report

⚠️ AI-generated triage. Validate before acting.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-approved ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants