> [!IMPORTANT]
> **Breaking Change:** Removed custom authentication in favour of msal. Old tokens will not work with this version and will require a new authentication flow.
- Account: you can now work with multiple users by changing `account.username` when using auth flow type authorization.
- Account: The username of the logged in use was previously held in `current_username`, it is now in `username` as per the previous bullet
- Connection methods `get_authorization_url` and `request_token` are now present in the `Account`object. You will no longer need to use the ones from the `Connection` object unless doing something fancy.
- Account and Connection: the authentication flow has changed and now returns different objects which need to be stored from and passed into `get_authorization_url` and `request_token` (if using those calls).
- TokenBackend: they now inherit from the msal cache system. You can now remove tokens, get access scopes from tokens, add a cryptography manager to encrypt and decrypt and much more.
- Scopes are now longer stored into the connection. Scopes are only needed when authenticating and will be stored inside the token data on the token backend.
- Scopes: You should no longer supply 'offline_access' as part of your requested scopes, this is added automatically by MSAL.
- Scopes are now passed in as `requested_scopes` rather than `scopes`
- Token: The token layout has substantially changes, so if you were interrogating it at all, you will need to adjust for the change.