Sharing power automate samples

[Solanki-Manish]

By submitting this pull request, you agree to the contribution guidelines

If you aren't familiar with how to contribute to open-source repositories using GitHub, or if you find the instructions on this page confusing, sign up for one of our Sharing is Caring events. It's completely free, and we'll guide you through the process.

To submit a pull request with multiple authors, make sure that at least one commit is a co-authored commit by adding a Co-authored-by: trailer to the commit's message. E.g.: Co-authored-by: name <[email protected]>

Put an x in all the items that apply ([x], without spaces), make notes next to any that haven't been addressed.

• Bug fix?
• New sample?
• Related issues: fixes #X, partially #Y, mentioned in #Z
• Needs API permissions?
• Has other prerequisites? (E.g. requires a list, document library, etc.)

What's in this Pull Request?

A sample to overcome 28 KB payload size limit for embedding an image in Microsoft Teams channel message using standard action in Power Automate.

Checklist

This checklist is mostly useful as a reminder of small things that can easily be forgotten – it is meant as a helpful tool rather than hoops to jump through.

Put an x in all the items that apply ([x], no spaces), make notes next to any that haven't been addressed.

• My pull request affects only ONE sample.
• I have updated the README file.
• My README has at least one static high-resolution screenshot (i.e. not a GIF)
• My README contains complete setup instructions, including pre-requisites and permissions required

[Katerina-Chernevskaya]

Hi @Solanki-Manish ,

Thank you for your contribution!

I've tried to create a solution from the source code and got the error:

It seems that some files are missing from the source code. Please update it according to the guideline and let me know once it is ready. I'll be happy to review and merge it!

Thank you!

[Katerina-Chernevskaya]

Hi @Solanki-Manish

Thank you for the contribution! I've created the solution and added the sample.json file.
I'm going to merge the PR.
Just a minor improvement for the future - please consider to move dynamic values (like SharePoint site, etc.) to the environment variables. This will make the import process strightforward, following best practices and exclude edit flow dtep.

Thanks again!

Regards,
Kate