Full Service Terms
Last updated: October 12, 2026
These terms set out what Power Portals LLC, doing business as Power Portals Pro ("we", "us"), does under a Full Service subscription, what we need from you, the access you give us to your Microsoft environment, and how we look after that access. Your subscription is governed by the Microsoft Standard Contract for the commercial marketplace, with our amendment to it, which you accept when you purchase it. These terms describe the service under that contract; where the two conflict on a legal matter, the Standard Contract as amended applies. When your subscription begins, we send you these terms as an engagement letter to sign.
1. The service
Full Service is the Power Portals Pro software, hosted and looked after by us.
- Licence. The Power Portals Pro licence for one portal, included in the subscription.
- Hosting. We run the portal on Microsoft Azure App Service in our own Azure subscription, in the United States unless we agree another Azure region with you. You need no Azure subscription of your own. The portal is served over HTTPS only, with TLS 1.2 as the minimum.
- Initial setup. Up to 20 hours of setup and configuration, starting from the getting-started checklist we send when your subscription begins.
- Ongoing support. Up to 5 hours a month for support, changes and maintenance. Unused hours don't carry over to the next month. Work beyond that is charged at USD 200 an hour, quoted in advance and done only with your agreement.
- Upgrades. We apply new Power Portals Pro releases and security fixes, including the managed solution in your Dataverse environment and the .NET runtime the portal runs on.
- Users. No per-user charge, however many people use the portal.
Availability and support are described on our service levels page.
2. Fees and term
- Fee. USD 1,495 a month per portal, billed monthly through your Microsoft Marketplace subscription.
- Term. 12 months from the date the subscription is activated. It then renews automatically for further 12-month terms unless it is ended as described in section 9. Full Service is only offered on annual terms; there is no month-to-month option.
- Changes to the fee apply only from the next renewal, with at least 90 days' notice before that renewal.
3. What we need from you
- Your Dataverse environment. The portal reads and writes your data there. You keep the environment and its Microsoft licensing.
- Administrators, once. A Global Administrator to approve our two applications (section 4), and a Dataverse System Administrator to create their application users and assign their roles. We can do this together on a call.
- Decisions and information, from the getting-started checklist: what the portal shows and collects, who can see what, your branding, and your timeline. Setup hours depend on these arriving in good time.
- Your domain, if you want one. If the portal is to run on your own address, someone who can add DNS records for it.
- Sign-in providers. If you offer Google or Facebook sign-in, the credentials for your own Google or Facebook registrations.
- A sending mailbox. An address the portal's emails come from (for example
noreply@yourcompany.com), set up as a shared mailbox in your Exchange Online. It needs no licence.
4. Access you give us
You give two of our Microsoft Entra applications access to your Dataverse environment. Both act as dedicated application users, not as any of your staff. Neither has any access to the rest of your Microsoft 365 tenant: no mail, files, Teams or directory data.
| Application | What it is for | Security role in your Dataverse |
|---|---|---|
| Power Portals Pro - App User | The portal itself, reading and writing your data as your portal's users are allowed to | Power Portals Pro Application User (from our managed solution), plus the column security profile the portal needs for its users' sign-in details, plus any role you approve for your own tables |
| Power Portals Pro - Deployment Admin | Us, installing and upgrading our managed solution and making the security changes your portal needs | System Administrator |
- System Administrator is broad. It lets the Deployment Admin read and change any data and configuration in the environment. We use it only for work under your subscription: installing and upgrading our solution, configuring the portal's security roles, table permissions and settings, and diagnosing problems you have raised with us. We do not use it to browse or export your business data except as a specific piece of work you have asked for needs.
- Data the portal reaches is only what has been configured for it, table by table and column by column. Nothing is exposed by default. Row-level restrictions are applied in the query sent to Dataverse, so records a portal user isn't entitled to never leave it.
- Other environments. If you give us access to more than one environment (for example a test environment), the same terms apply to each.
5. How we protect that access
- There are no passwords or secrets for either application. The portal signs in as the App User using an Azure managed identity that exists only on our hosting, so there is no secret that could be copied, leaked or expire. We sign in as the Deployment Admin using a certificate whose private key is held in Azure Key Vault and cannot be exported from it. It is renewed every 12 months.
- Authorised staff only. Only authorised Power Portals Pro staff can use the Deployment Admin certificate, each through their own sign-in with multi-factor authentication.
- In your own audit log, changes we make appear as "Power Portals Pro - Deployment Admin".
- Your own sign-in settings stay yours. Your administrators' sign-ins and any conditional access policies you apply to your own staff are unaffected.
6. Your controls
- You always have control of both applications: you can disable or re-enable either application user in your Dataverse environment at any time. Disabling the App User stops the portal reaching your data immediately. Disabling the Deployment Admin stops us making changes, including upgrades and fixes, until it is enabled again; the running portal is unaffected.
- Approval of changes. We agree significant changes with you before making them: anything that changes what portal users can see or do, or that changes your environment's security configuration outside the portal.
7. Your data
- Your data stays in your Dataverse environment. The hosting keeps no copy of your business data. The portal reads and writes it on each request, holding only short-lived cached data in memory.
- Portal user accounts are contacts in your Dataverse. Passwords are stored only as salted hashes, never in readable form, and never outside your environment.
- What we receive outside the portal: a periodic licence check sends your organisation id, the portal's web address and its licence key to powerportalspro.com. Application logs from the hosting (requests, errors and performance) are kept for at least 30 days and no more than 90 days, and used only to operate and support the portal.
- Backups of your data are Microsoft's, as part of Dataverse. The portal holds no separate database to back up.
- How we process personal data, and who our subprocessors are, is set out in our data processing agreement and subprocessor list.
8. Security incidents
If we become aware of any unauthorised access to your environment through our applications, or to the hosting that runs your portal, we will tell you within 72 hours, with what we know at that point, and keep you informed as we learn more.
9. Ending the subscription
- At the end of a term. Either of us may end the subscription at the end of the current 12-month term. You do it by turning off automatic renewal for the subscription in Microsoft Marketplace before the renewal date; we do it by telling you in writing at least 90 days before that date and cancelling the subscription so it does not renew. Apart from the cancellation window Microsoft Marketplace itself provides (currently within 72 hours of a purchase or renewal), it does not end part-way through a term.
- When it ends, we stop and remove the hosting, and with it the portal. You disable or delete both application users in your Dataverse environment, and remove both applications from your Microsoft Entra tenant (under Enterprise applications); we can walk you through it. Our managed solution and anything configured for the portal remain in your environment unless you ask us to remove them as part of the last month's support hours.
- Moving to self-hosting. If you would rather run the portal yourself with a Power Portals Pro licence, we will help with the move. That needs your own app registration, because our applications are only used where we host.
10. Contact
Power Portals LLC (doing business as Power Portals Pro)
2998 E Lakeside Dr, Eagle Mountain, UT 84005
Support: support@powerportalspro.com
Contact: Steven Rasmussen, srasmussen@powerportalspro.com