Jump to content

Recommended Posts

Posted

Before I go asking software resellers and getting sales spam, we are currently using older OVS-ES deviceOS+cals+office+365apps+intune1+entra1 .  Looking at  a new agreement later this year, so thinking A3 via Chest instead.  I see that there is a staff count reconciliation date of 1st November, what happens if you get new staff after this (i.e. agreement is for 90EQU and at 1st Nov still 90EQU but in December 2 extra EQU join so now need 92 licenses)?  Are there grace logons available or are you allowed to go over your assigned A3 "without loss of function" until 1st Nov rolls about again (i.e. will 365 admin portal let you go 92/90)?  I've not been in a position where our allocated A1 or M365 are even close to xx/yy licenses so not had this issue. 

 

Is there a rough anecdotal "over XX EQU users is generally better to go Chest EES"?

 

Can you still get MAK keys from MS for devices that don't have embedded licenses (we have a couple of small "has device sticker windows license but not an embedded one" appliances that do use windows such as digital signs)?  Whilst we don't have any, I assume all windows logons will need to be 365 and not local logons (as i'm not sure how they could be licensed as a local logon unless said MAK key exists and an "honour" license)

Posted

M365 licences are per-user and must be assigned in the M365 portal like your current A1s are, but I'm pretty sure you can add licences mid-term as monthly licences rather than annual ones.

 

You won't need MAKs as M365 A3 comes with "Subscription activation", that will take any device that has an activated Windows Pro or Pro Education licence and upgrade it to Enterprise or Education respectively when an A3 user logs in.

 

You can technically set up local accounts, the DfE did on their Intune image they gave out on the COVID laptops, but it's generally best to use A3-licenced accounts, especially if you want to use Microsoft Office, as that requires the user to be logged in with their Entra account with the M365 Apps licence (which is part of the A3 licence).

 

Essentially, it looks like you're swapping the accounts in M365 that currently have the licences separately to all be on the A3 licence which has them all bundled together.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...