It could be simply that your adminstrator is particularly draconic and wants to approve every single app individually. And because Thunderbird changed scopes, it needs to be re-approved.
> We are not granted EWS permissions anymore for security reasons
When you say "we", I assume you mean your company's employees. Did your administration specifically disable this feature, for your domain?
Does he allow IMAP and SMTP? If so, what is his rationale? EWS allowes OAuth2 just as IMAP does, and EWS is based on https (SSL), so don't see a valid reason why EWS would be disabled. Could you please share what your admin said about it, and his rationale?
I know that many admins and domains disable login via EWS, IMAP, or other specific protocols. But I have never heard that the OAuth2 scope for EWS is specifically forbidden.
Bug 1908866 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
It could be simply that your adminstrator is particularly draconic and wants to approve every single app individually (which is extremely unhealthy for the software ecosystem, because it favors monopolists). And because Thunderbird changed scopes, it needs to be re-approved.
> We are not granted EWS permissions anymore for security reasons
When you say "we", I assume you mean your company's employees. Did your administration specifically disable this feature, for your domain?
Does he allow IMAP and SMTP? If so, what is his rationale? EWS allowes OAuth2 just as IMAP does, and EWS is based on https (SSL), so don't see a valid reason why EWS would be disabled. Could you please share what your admin said about it, and his rationale?
I know that many admins and domains disable login via EWS, IMAP, or other specific protocols. But I have never heard that the OAuth2 scope for EWS is specifically forbidden.
It could be simply that your adminstrator is particularly draconic and wants to approve every single app individually (which is extremely unhealthy for the software ecosystem, because it favors monopolists). And because Thunderbird changed scopes, it needs to be re-approved.
> We are not granted EWS permissions anymore for security reasons
When you say "we", I assume you mean your company's employees. Did your administrator specifically disable this feature, for your domain?
Does he allow IMAP and SMTP? If so, what is his rationale? EWS allows OAuth2 just as IMAP does, and EWS is based on https (SSL), so don't see a good reason why EWS would be disabled. Could you please share what your admin said about it, and his rationale?
I know that many admins and domains disable login via EWS, IMAP, or other specific protocols. But I have never heard that the OAuth2 scope for EWS is specifically forbidden.
It could be simply that your adminstrator is particularly draconic and wants to approve every single app individually (which is extremely unhealthy for the software ecosystem, because it favors monopolists). And because Thunderbird changed scopes, it needs to be re-approved.
> We are not granted EWS permissions anymore for security reasons
When you say "we", I assume you mean your company's employees. Did your administrator specifically disable this feature, for your domain?
Does he allow IMAP and SMTP? If so, what is his rationale? EWS allows OAuth2 just as IMAP does, and EWS is based on https (SSL), so don't see a good reason why EWS would be disabled. Could you please share what your admin said about it, and his rationale?
I know that many admins and domains disable login via EWS, IMAP, or other specific protocols. But I have never heard that the OAuth2 scope for EWS is specifically forbidden. I suspect it's just a "every app must be approved" policy, as mentioned at the start.
It could be simply that your adminstrator is particularly draconic and wants to approve every single app individually (which is extremely unhealthy for the software ecosystem, because it favors monopolists). And because Thunderbird changed scopes, it needs to be re-approved.
> We are not granted EWS permissions anymore for security reasons
When you say "we", I assume you mean your company's employees. Did your administrator specifically disable this feature, for your domain?
Does he allow IMAP and SMTP? If so, what is his rationale? EWS allows OAuth2 just as IMAP does, and EWS is based on https (SSL), so don't see a good reason why EWS would be disabled. Could you please share what your admin said about it, and his rationale?
I know that many admins and domains disable login via EWS, IMAP, or other specific protocols. But I have never heard that the OAuth2 scope for EWS is specifically forbidden.
It could be simply that your adminstrator is particularly draconic and wants to approve every single app individually (which is extremely unhealthy for the software ecosystem, because it favors monopolists). And because Thunderbird changed scopes, it needs to be re-approved. Your screenshot suggests that.
> We are not granted EWS permissions anymore for security reasons
When you say "we", I assume you mean your company's employees. Did your administrator specifically disable this feature, for your domain?
Does he allow IMAP and SMTP? If so, what is his rationale? EWS allows OAuth2 just as IMAP does, and EWS is based on https (SSL), so don't see a good reason why EWS would be disabled. Could you please share what your admin said about it, and his rationale?
I know that many admins and domains disable login via EWS, IMAP, or other specific protocols. But I have never heard that the OAuth2 scope for EWS is specifically forbidden.