Updated "Getting Started" documentation

[sdelgadoc]

Background
One of the biggest barriers for beginners to get started with the python-o365 library is setting up OAuth authentication. The “Getting Started” guide referenced the outdated apps.dev.microsoft.com portal, could include additional detail, and did not include an example of how to use the library. In addition, other tools that use the python-o365 library can benefit from improved getting started instructions.

Challenge
With the transition to the Microsoft Entra Admin Center, the old instructions might confuse users by pointing them toward a deprecated portal. A more detailed guide could help developers navigate the new Microsoft Entra Admin Center and quickly understand python-o365 installation and usage.

Changes

• Updated Microsoft Entra Admin Center References

  • Removed references to the old apps.dev.microsoft.com portal.
  • Provided detailed, step-by-step instructions for registering applications in the new Microsoft Entra Admin Center (creating apps, generating secrets, adding redirect URIs, and configuring permissions).

• Expanded Basic Usage Section

  • Included a complete Python code example demonstrating how to instantiate Account and send an email with python-o365.
  • Used fenced code blocks for improved clarity.

[alejcas]

Good job! thank you!

[sdelgadoc]

Hi @alejcas, thanks for accepting the PR! Did you have a chance to run make html when merging so the getting_started.rst file in the source folder generates a new getting_started.html file in the latest folder? The HTML file still shows the previous version of the content.

[alejcas]

Hi @alejcas, thanks for accepting the PR! Did you have a chance to run make html when merging so the getting_started.rst file in the source folder generates a new getting_started.html file in the latest folder? The HTML file still shows the previous version of the content.

I'm having some hard weeks this days. I'll do it asap.

[sdelgadoc]

This is not urgent @alejcas. No need to expedite. Thank you for your help!

[alejcas]

If you want or/and have time, setting this info into the readme could also be very good for beginners.

thanks

[sdelgadoc]

Absolutely! I have added the app registration steps to the README in PR #1118. Let me know if you have any edits or questions!

[alejcas]

Unfortunately the doc build step is not working although there are no errors.
I don't know why, but I can't get the docs to be published with the latest changes.

Do you know why?

[RogerSelwyn]

When I look at one of my page build jobs I get the below:

When I look at yours there is no build step within the build step.

Could it be that the makefile/sphinx is not supported by GitHub anymore, I can see it was created a long time ago.

[RogerSelwyn]

It looks to me like there should be a GitHub action to create the pages, and then use the GitHub pages settings to deploy it. I haven't got time to try it out on my fork this week, but if you don't figure it out I'll try it next week.

https://coderefinery.github.io/documentation/gh_workflow/

Edit: Did you lose the action when you moved to this repository a long time ago, or was someone running it by hand?

[sdelgadoc]

Hey @alejcas, I'm not familiar with the workflow but the feedback from @RogerSelwyn looks helpful.

[RogerSelwyn]

I have created this PR to add key missing api docs and automate the publication - #1129