improvement: refactor the API to MS Graph for clarity and separate concerns

[Samlant]

Describe the fault
The API for MS Graph is well-drafted, however the front-facing interface is redundant, with a model that's more ambiguous than I'm comfortable with. The order of execution can be made clearer, the status of the API can be shown better, and error-handling of the API is currently poor and messy.

Expected behavior
Draft a new front-facing interface to make it easier for Presenter to interact with, with methods that demonstrate a clear, linear progression of tasks that makes it apparent when and how the API is functioning. Error handling should be done in a helpful manner, catching specific exceptions, likely based off of the error responses... when MS decides to use a useful one...