Nexus Productivty: leveraging the power of Microsoft graph and Azure ... - #825

Hi @mahasch - this PR only contains an empty folder - did you commit your changes?

Hi @BobGerman Apologies, I didn't realise that it had submitted as a sub module and that the file was empty. I pushed again and it seems the files are there now. Could you please check if this is alright? Thank you

Thanks - I got more this time!
There still seem to be some missing pieces here however.

1. If this is a tab, please rename your project from app-nexus-productivity to tab-nexus-productivity. The "app-" naming convention is for solutions that include multiple capabilities such as a tab and a bot or a tab and a message extension.
   This and other details are contained in our contribution guidelines: https://github.com/pnp/teams-dev-samples/blob/main/CONTRIBUTING.md

2. Please use one of our README templates, which will guide you to include more complete information in your README file, such as instructions for building the solution.
   All samples need to include build instructions so people can use your sample.

If your solution does not use the Teams Toolkit, you'll want to start with the sample README.md and .gitignore found here: https://github.com/pnp/teams-dev-samples/tree/main/samples/_SAMPLE_templates/dotnet-sample

3. All Teams apps have a Teams app manifest. Where is yours?

4. Please include a .gitignore file (gitignore.txt is not correct - the VS sample template in this repo includes a .gitignore file that should work). After building your solution without .gitignore, 626 files are changed in the repo - these would affect other developers who subsequently used the solution.

This looks like a really cool solution - thanks very much for submitting - getting close for sure!