[Users] office365 oauth2

[David Fletcher]

>dmacdoug <dmacdoug at usc.edu> wrote:
>
>> Step 1 is to login to portal.azure.com which works.

Hi Don,

I wonder if this very first step, which appears to work, is also where
things go wrong. Are you connecting to Azure using your university
login? That means you're then restricted by the permissions granted to
you by the university - for example they may not want you to create
applications under their name.

However, there's no need to use the university Azure account to create
your Claws Mail ClientID. Just as Thunderbird's Client ID is not
created under an Azure account linked to your university.

I would suggest using a personal Azure account, under which you can set
up the ClientID exactly as you need for Claws. You then authorise Claws
to connect to your university email using that ClientID. This way the
university just sees an email client being authorised to read/write
email. It does not see an whole application being created under their
name/account/tenancy or whatever the Microsoft term for this is.

In the Claw Oauth2 FAQ for Microsoft if says "set Supported account
types to the most premissive option: "Accounts in any organizational
directory and personal Microsoft accounts"". This is the part that
lets you create the ClientID under one account (e.g. your personal Azure
account), but create the ClientID that will allow you to connect to
other organisations (e.g. your university).

See if this works, best wishes,

David.