Re: Making an app available outside company without gvining access to any other part of office365
Thanks for clarifying. I made a dummy account to my own gmnail address so I can experiment with all this without bothersome to and fro communication until it all works.
Strange enough with this account I can change password within azure directory (is gmail special?).
I found out that I have to login with just the email address without the onmicrosoft extension (again, because it is gmail?)
My app uses a sharepoint document folder, can send email and retrieves users from teams.
What I now get when trying to open the app is permission for
-Outlook
authentication fails with
REST API wordt nog niet ondersteund voor dit pastvak. Deze fout kan optreden voor sandbox-accounts (test) of voor accounts die zich op een specifieke (on-premises) mailserver bevinden.
[Rest API is not yet supported for this inbox. This error can occur for sanbox accounts (test) or for accounts that are on a specific (on premis) mailserver]
-Teams
authentication fails with
User Login. Teams is disabled for your tenant.
-Onedrive
authentication fails with
Er is een fout opgetreden tijdens de verificatie.
[An error has occurred during verification]
Is it possible to remedy these hurdles or to selectively make the app not need these based on user without making a seperate app?
I even added the user to a team. Sharepoint is no problem and I thouht sharepoint and onedrive are similar. Fot both access by external users is allowed in the administration centre. I temporarily enabled a office e3 account for the user without difference. In the admin centre for teams access by external users is allowed.