Hi Bram 
No problem; this stuff can get more than a little complicated! 
So Auth0 issued access tokens are designed for use by first-party APIs - i.e. the APIs you build yourself. They are completely separate from any tokens required for accessing third-party APIs (such as the OneDrive APIs built by Microsoft). Most of the documentation you will see regarding Auth0 examples, et al, will simply talk about the set of tokens Auth0 issues: namely access tokens for first-party APIs, and the id tokens issued to first-party applications (as in those applications you build yourself). Auth0 does not issue tokens on behalf of anyone else.
What Auth0 can do is provide access to any third-party access tokens generated as part of them (said third-party) also acting as an Identity Provider - e.g. windowslive acting as the identity provider in your case. However these third-party tokens really shouldn’t be used outside of an Auth0 extensibility context, as there a numerous caveats.
Because third-party access tokens are totally separate from Auth0 (first-party) access tokens, renewing them with a call to the third-party authorization server won’t affect the ones generated by Auth0. It may however affect the (third-party) ones stored by Auth0. And that really depends on the implementation details of the third party authorization server - in essence whatever its token refresh policy is and how it handles that . In general, access tokens themselves are typically designed to be short lived anyway, so will naturally expire - regardless if they’re generated by Auth0 or some third-party.
Hope that helps 