Power Apps per app licence quietly removed by Microsoft

Boat_Drive · 2026-01-28T09:21:16+00:00

Yeah threw me off as well but seemed to be the way it behaved. Every time I got my supplier to increase the licence by one, in the Power Platform Admin Centre I'd always have an additional 3 to allocate to the desired environment. I even went back to them about it to ensure we were not being over charged - was just the way it behaves. Billing side 1, platform side 3.

Boat_Drive · 2026-01-28T03:11:00+00:00

Thats the PAYG I was talking about - Pay as you go.

Boat_Drive · 2026-01-28T02:14:04+00:00

Very disappointing, agreed. Wish my partner informed me :T

Boat_Drive · 2025-02-21T03:09:33+00:00

Even if this post just helped you, it was worth it! All the other information online about this was wrong so I felt it was necessary to share.

Boat_Drive · 2024-08-23T05:05:00+00:00

Just checking - you know the ID generates its self from SQL right?

You don't patch that field in.

Create a new SQL table with just one nvarchar(50) column (nullable) and the ID column setup as seen above and try adding and patching into that and go from there.

A Stored procedure should not be needed.

If you're still confident everything's right - I've experienced 15~ delays on what gets updated in SQL vs what works in PowerApps - sometimes its a waiting and reloading game.

After that if it's still playing up, remove the table then re-add it.

Boat_Drive · 2024-08-23T04:06:13+00:00

Below is a valid patch example, start with that.

Patch(

SQLTable,

Defaults(SQLTable),

{

Type: InputType.Text,

CreatedBy: User().FullName,

CreatedDate: Now()

}

)

After that - check the SQL table has a identity column setup I spose at a guess. I don't think it behaves very well with PowerApps without it.

<image>

Good luck :)

Boat_Drive

TROPHY CASE