Deploy a 1Password Connect server on Azure

Thanks @Joris_1P! The command I'm issuing is: https://.azurewebsites.net:8080/v1/vaults
I'm calling it from Power Automate, this is what the flow looks like (apologies for the lame obfuscation attempt, using the tools I had in the moment)

The command I'm issuing is: https://.azurewebsites.net:8080/v1/vaults

Looking at the screenshot, I am assuming that has your custom domain after https:// and before .azurewbesites?

1. Does Power Automate return any error? If so, what does it return?
2. Could you try the URL without :8080?
3. What happens if you visit the /health route in your web browser? E.g. https://my-connect.azurewebsites.net/health

PS. I've edited your screenshot to mask it a bit better. Because Connect tokens are JSON, even sharing them partially could be problematic. I recommend revoking the current token.

Correct - that was my custom domain in the URL. And thank you for doing a better job of obfuscating my screenshot. :-)

I removed the 8080, and at least this time got an invalid bearer token error - so that means I was at least able to speak to the web app, so that's progress!

My own stuff-up with the access token there. Got it working, thank you!!!

You are welcome! Good to hear it's working now. Let me know if you run into anything else.

Joris

So, fun times discovering that using the Connect Server approach is quite manual in terms of giving access to vaults, creating a new access token each time, etc.
Any chance you've tried putting the CLI into an Azure Web App? :-)

We are working on improving the possibilities of using the 1Password CLI in these kinds of environments. As part of this, we are currently testing out a new service accounts feature in a small-scale private beta. If this is something you are interested in testing, you can sign up https://forms.gle/G1e9vib6UEQbTYb59.