Skip to content

Add MicrosoftOfficeFilesParser independent publisher connector by Steven Soe #3936

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
Open
wants to merge 6 commits into
base: dev
Choose a base branch
from
Open

Add MicrosoftOfficeFilesParser independent publisher connector by Steven Soe #3936

wants to merge 6 commits into from

Conversation

ssdevkit
Copy link

Pull Request Description

Overview

This pull request adds a new Independent Publisher connector named MicrosoftOfficeFilesParser. The connector enables parsing of Microsoft Word and Excel files by accepting base64-encoded content and returning extracted text or worksheet data in a structured format. It is designed to be used in Power Automate, Power Apps, and Azure Logic Apps for document content extraction and automation scenarios.

Features

  • Parses Word documents and returns extracted text content.
  • Parses Excel spreadsheets and returns all worksheet names along with their data as 2D arrays.
  • Supports base64 encoded file content input for both Word and Excel formats.
  • Provides clear response schemas for predictable integration in workflows.
  • Includes a custom icon and metadata aligned with Microsoft Power Platform guidelines.

Testing and Validation

  • I have thoroughly tested the MicrosoftOfficeFilesParser connector by deploying it in Power Automate.
  • Multiple test flows were created to validate key operations including Word document parsing and Excel spreadsheet parsing.
  • All operations executed successfully, returning expected outputs without errors.
  • Screenshots of the test flows with successful operation runs are included in this pull request for your review.
  • The OpenAPI (Swagger) definition was validated using the paconn validate tool to ensure compliance with the connector standards.
  • This connector is ready for certification and publishing as an Independent Publisher connector.

Attestations

  • I attest that this connector does not currently exist in the Power Platform repository.
  • I attest that the connector works and I have verified all operations through testing.
  • I attest that I have included detailed descriptions for all operations and parameters in the swagger file.
  • I attest that I have added response schemas to all actions, except where responses are dynamic.
  • I have validated the swagger file using the official validator tool.
  • As an independent publisher connector, I have set "iconBrandColor": "#da3b01" in the API properties file.
  • I confirm that I am not submitting a connector icon that violates any trademarks or copyrights.

Please review and provide feedback or approve for merge. Thank you!

@ssdevkit ssdevkit requested a review from a team as a code owner July 17, 2025 04:13
@ssdevkit
Copy link
Author

@microsoft-github-policy-service agree

@troystaylor
Copy link
Contributor

Hi Steven,
It appears that you are the owner of the API service - is that correct?

Troy

@ssdevkit
Copy link
Author

ssdevkit commented Jul 17, 2025 via email

@troystaylor
Copy link
Contributor

Hi Steven,
Then you will need to submit the connector as a Certified Publisher instead of as an Independent Publisher:
https://learn.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification

Troy

@ssdevkit
Copy link
Author

ssdevkit commented Jul 17, 2025 via email

@troystaylor
Copy link
Contributor

Hi Steven,
Apologies (it is late here on the east coast of the US), yes I meant verified publisher.

Troy

@ssdevkit
Copy link
Author

ssdevkit commented Jul 17, 2025 via email

@ssdevkit
Copy link
Author

Hi Troy,

I have resubmitted for review under Certified-connector folder.
Thanks.

@ssdevkit
Copy link
Author

Hi @troystaylor Would like to check if my resubmission is all good please. Thanks a lot.

@troystaylor
Copy link
Contributor

Hi Steven,
I’m not on the certification team - @vmanoharas can you please comment?

Troy

@ssdevkit
Copy link
Author

Many thanks @troystaylor and @vmanoharas . Look forward to feedback.

@certificationteam
Copy link
Collaborator

Hi @ssdevkit,

Thank you for submitting your connector. However, it is observed that the files are not as expected. Kindly refer the screenshot below.

image

Please refer below links and submit your artifacts.

https://github.com/microsoft/PowerPlatformConnectors/blob/dev/README.md

https://github.com/microsoft/PowerPlatformConnectors?tab=readme-ov-file#certified-connectors

@ssdevkit
Copy link
Author

Hi @certificationteam Thank you for the feedback. I have updated the submission to reflect on correct folders.
Kind regards!

@ssdevkit
Copy link
Author

Hi @certificationteam Would like to check if my submission is all good please?
Many thanks.

@certificationteam
Copy link
Collaborator

Hi @ssdevkit,,

Unfortunately, the folder structure is not as expected, kindly refer this link and update them.

https://github.com/microsoft/PowerPlatformConnectors/tree/dev/templates/certified-connectors

image

@ssdevkit
Copy link
Author

Hi @certificationteam - I have now updated my submission. Please help to check.

@ssdevkit
Copy link
Author

ssdevkit commented Aug 2, 2025

Hi @certificationteam I really would like to get feedback on my submission as it has taken awhile. Many thanks!

vmanoharas
vmanoharas reviewed Aug 13, 2025
View reviewed changes
Copy link
Contributor

@vmanoharas vmanoharas left a comment

Choose a reason for hiding this comment

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

Hi @ssdevkit,

Please address review comments.

certified-connectors/MicrosoftOfficeFilesParser/apiDefinition.swagger.json
},
{
"propertyName": "Categories",
"propertyValue": "Document Processing, Excel, Word"
Copy link
Contributor

Choose a reason for hiding this comment

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

Please fix the below error:

##[error]The connector category is invalid. Available categories are: [AI, Business Management, Business Intelligence, Collaboration, Commerce, Communication, Content and Files, Finance, Data, Human Resources, Internet of Things, IT Operations, Lifestyle and Entertainment, Marketing, Productivity, Sales and CRM, Security, Social Media, Website]. ValuePath: /x-ms-connector-metadata/2/propertyValue

certified-connectors/MicrosoftOfficeFilesParser/apiDefinition.swagger.json
"swagger": "2.0",
"info": {
"version": "1.0",
"title": "MicrosoftOffice Files Parser",
Copy link
Contributor

Choose a reason for hiding this comment

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

Please remove reserved word "Microsoft".

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

@vmanoharas vmanoharas vmanoharas left review comments

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ssdevkit @troystaylor @certificationteam @vmanoharas