Hi,
I’m working with a client who uses a third party to manage their Microsoft 365 platform. Until now, we’ve been using one of the manager’s login accounts to authenticate the OneDrive connections.
The third party has requested that we stop using this account, so I proposed creating a dedicated app account and providing the Client ID, Tenant ID, and Secret. I entered these details into Make, but it’s still prompting me to log in when saving the module.
I’m a bit confused, as I thought this setup would be a more secure way to connect without relying on a user account. Am I missing something here?
Welcome to the Make community!
You aren’t creating a new “account” – you have only created a custom OneDrive OAuth “connector” app to replace Make’s default OAuth connection. You’ll still need them to login via that app to authorise the connection.
You can also learn more about OAuth in these Make Academy units:
API calls with HTTP modules
- API and Endpoints
- Header and body
- Multipart/form-data
- OAuth 2.0
- Make API
— @samliew
1 Like
Thanks for the response. Is there a way to connect without using accounts and licenses do you know ? Its problematic when passwords are changed if it relies on user accounts
If MS/OneDrive decides to revoke OAuth connections when the account password is changed, then there is no way around it if there are no other forms of authentication provided by MS/OneDrive.
You did not mention that the user changed their password earlier, breaking the OAuth connection?
Hope that gets you started. If you are still having trouble, please provide more details and I’ll see if I can help.
— @samliew