Back to Community Threads
Auto-provision Members
Idea shared by Christopher Smith - 5/16/2026 at 10:37 AM
Under Consideration
C
Is there a way to automatically provision members via Entra or an API?
Ron Raley Replied
5/16/2026 at 4:36 PM
Employee Post
This can certainly be done, however, only about 3 percent of our customers use Microsoft Single-Sign-On. So it comes down to usage.
Ron Raley
Firehouse Solutions
P.O. Box 911
Leonardtown, MD 20650

Office: 301-475-1900
Email: Ron@FirehouseSolutions.com
C
Any further adoption consideration for this? Or an API available that I could write my own automation hook?
Ron Raley Replied
8/18/2026 at 6:01 PM
Employee Post
Due to the mere fractional usage of customers that use single sign-on, auto-provision just isn't a major priority at this time. Lets say hypothetically if it deployed now, the fractional gets even smaller of those who use it.

We can revisit this as more customers adopt single sign on, which I believe is growing. 
Ron Raley
Firehouse Solutions
P.O. Box 911
Leonardtown, MD 20650

Office: 301-475-1900
Email: Ron@FirehouseSolutions.com
J
Chris... I wanted to see this too at some point. I think I can use firehouse solutions new API to send to Microsoft once an account is created in Firehouse. I haven't done it yet but it is on my to due list
C
Yeah, I am going to look more into the API. Our problem is that we utilize Entra as the source of truth for everything else. This switches that pattern for us. Also looke like the API endpoints are all GET, so a job in Azure would likely need to poll the API, run a job, then create the user in entra, etc. Not 100% sure the juice is worth the squeeze there.
Ron Raley Replied
11/4/2026 at 12:40 PM
Employee Post
We may likely graduate to NEW and UPDATE, but wanted to stick with READ-ONLY on the API just to get our feet wet and see how many customers will use it.
Ron Raley
Firehouse Solutions
P.O. Box 911
Leonardtown, MD 20650

Office: 301-475-1900
Email: Ron@FirehouseSolutions.com
J
Ron I understand completely what you are saying. Chris and I both seem to provision on the Microsoft side. I am not sure how they do it, but I have a form our users fill out. It gets submitted I approve it through email. It creates an email address, assigns microsoft license, and assigns them to the members distribution group. Then it creates a zello account for them. Then I have to say please go to firehouse solutions and create an account there to approve. I would love to have the form just send it over and auto provision. Thank you for all that you all our doing loving the new updates
C
Currently, I have a powershell script (not sexy at all) that does all of the provisioning for us. I haven't had the time to look too deep into it, but I was considering a Form/Power Automate flow or rolling ChiefOnboarding.

Our current process and records management is very disaggregated with lots of duplicated steps. We just built, and are currently testing, a custom application for the firehouse that would serve not only LOSAP records management, but also membership, training, docs, etc. We roughly sketched out a Applicant tracker module as well that would have a workflow that once they are voted in would auto-provision the account by calling the M$ Graph API.

Seeing what you guys are doing here is making me re-think a lot of the custom work we are doing. That being said, there is something about having all my stuff in an Azure SQL DB that I own versus vendor lock-in.

Long-winded answer, I know lol. Ron, do you guys have any mockups, ideas, use-cases for the API?
Ron Raley Replied
11/8/2026 at 1:10 PM
Employee Post
There is another way to do this.  Automatic account creation can happen upon the first sign-on.  So the website will create an account under the pretense that the user should have access (since logging in with myfiredeptdomain.com).

However, Google will only send you the name and email address.  Nothing else.  So this is hurtful for the Online Members to gather phone number and address.  I am unsure if Microsoft sends more or less info.  There could be a way to get more information from Google and Microsoft, but haven't researched yet.
Ron Raley
Firehouse Solutions
P.O. Box 911
Leonardtown, MD 20650

Office: 301-475-1900
Email: Ron@FirehouseSolutions.com
J
Ron,

If you have an incoming API into firehouse solutions that allows access to all the account fields. Then it can 100% be done through Microsoft. A microsoft form captures all the information that the user fills out. It then goes through Microsoft Power Automate. Power Automate will parse the information from the Microsoft Form and send it to Firehouse Solutions API. That is a high level overview.

Jay
J
This is power automate you just put in how to handle the flow and it runs.
Back to Community Threads

Reply to Thread

Enter the verification text
Related Knowledge Base Articles
Training Center - User ManualMembers Area
How to Create a DatabaseMembers Area
Managing MembersMembers Area
Applying for Access to the Members AreaMembers Area
How to Create Sign Up SheetsMembers Area