Microsoft 365 allows expiry from 14 to 730 days, and Okta allows up to 999 days, with minimum length and history limits as well.
Key takeaways
- Microsoft 365 expiry runs from 14 to 730 days, or passwords can be set to never expire.
- Okta sets minimum length from 4 to 30 characters (default 8) and history from 1 to 30 passwords.
- Confirm Microsoft 365 length and history settings in your admin center, since the page checked here does not give them.
- Confirm the admin role, record current values, and change one platform at a time.
Who this post is for
If you run a small firm's sales team and also hold the user administrator role in Microsoft 365 or Okta, you are probably the person who sets the password rules your reps live with. In a small firm that job lands on the revenue leader, who is already busy with pipeline reviews, forecasts, and customer calls.
Those rules usually need to be in place before quarter end. Making the change early, and making it deliberately, avoids a rushed setting you have to explain later.
This post compares three password limits that matter in both products: how long a password can last before it expires, how short a minimum length can be, and how many earlier passwords the system remembers. For each limit I quote what the official pages say and explain what it means for a small team. Where the page I checked does not give a limit, I say so instead of guessing.
Nothing here replaces the screen in your own admin center. Check the current menu before you change anything, because product menus move and labels change between releases.
The example we will follow
Throughout this post we will follow Northfield Sales. Northfield is a made-up firm with a small team of reps, one revenue leader, and a shared sales mailbox. It uses Microsoft 365 for email and calendars, and it uses Okta to sign reps into its sales tools. The revenue leader holds the user administrator role in both places.
Northfield has three goals before quarter end. It wants fewer forced password changes in the middle of a deal, a minimum length well above the default, and a rule that stops reps from cycling back through an old password. Each section takes one goal and checks what the platform allows. Where a platform gives a range, Northfield picks a value on purpose and writes down why.
Limit 1: how long a password can last
Microsoft 365 starts from a simple choice. The Microsoft Learn page on the password expiration policy says, "As a user administrator, you can make user passwords expire after a certain number of days, or set passwords to never expire." Microsoft Learn: Set the password expiration policy So the revenue leader can choose expiry or no expiry. If they choose expiry, the same page says to "Choose a number of days from 14 to 730, and then select Save." Microsoft Learn: Set the password expiration policy
The page also gives the path in the admin center. It says, "In the Org Settings page, select the Security and Privacy tab." and then, "In the Security and Privacy tab, select Password expiration policy." Microsoft Learn: Set the password expiration policy It adds, "You must be a user administrator to perform these steps." Microsoft Learn: Set the password expiration policy Northfield's revenue leader holds that role, so the change belongs to them and does not need to go to an outside IT contractor.
Northfield's first instinct is to pick the shortest expiry, 14 days, because it sounds safest. That would force every rep to change a password about every two weeks. Reps who travel or work from a phone would hit lockouts far more often, and a locked rep cannot work a deal.
Northfield also has a shared sales mailbox, and a shared account raises a practical question. Whoever holds the password for that mailbox has to update it on every device that uses it, and a forced change can leave one device signed out without anyone noticing until a deal email is missed. A longer interval means that disruption happens less often. For checks to run after a shared login changes, see Access log checks.
So Northfield picks 730 days, the top of the range, and puts its effort into password length and a password manager instead. This is a judgment call. The source gives the range, not the right answer for your team. If your firm has a compliance requirement that sets a shorter interval, that requirement wins over this example, and you should set the value your obligations need.
Okta also lets you set an expiration, but the limit is different. Okta's page on configuring password policies says, "You can configure this setting for up to 999 days." Okta: Configure a password policy Read that line next to the expiration setting it describes before you rely on it, because the page's wording is specific to that setting.
The same page also says, "When used with the default expiration setting of 0, the user must set a new password before signing in again." Okta: Configure a password policy That line describes how the default of 0 behaves. It does not say whether passwords expire under that default, so check the full page before you rely on it.
For Northfield on Okta, the leader sets the longest value Okta allows. That keeps the logic the same on both platforms: a long expiry interval, paired with strong passwords and a password manager. The leader writes down both values so the rollout note explains the choice.
Limit 2: the minimum length
Length is where the two products differ most clearly in what the official pages give you. Okta's page says, "Enter a minimum password length of four to 30 characters (the default minimum is eight characters)." Okta: Configure a password policy A four-character minimum is too short for a sales account that can see customer records, so the eight-character default is the floor, not the goal.
Northfield raises the minimum well above the default and stays under the 30-character ceiling. The reason is practical. Length usually matters more than complicated character rules, because a longer passphrase is harder to guess and still possible to remember. A rep typing on a phone between calls can handle a longer phrase more easily than a short string full of symbols, especially if they cannot paste it.
A password manager changes the problem. The rep does not have to remember or type a long password every time, because the manager fills it in. The UK's National Cyber Security Centre puts the core idea plainly: "You only need to remember one primary password, and the manager takes care of the rest." NCSC: Trusting the tech That quote supports the approach. It does not set a length for your firm, so the number is still your decision within the range Okta allows.
For Microsoft 365, the page I checked covers expiration, not minimum length. It does not give a length range, so this post does not state one. Look in your Microsoft 365 admin center for the password settings that apply to your tenant before you tell reps a number. If you cannot find a length setting there, say so in your rollout note rather than assume one exists or what it allows.
For the rollout, set a clear date for when new rules apply.
Limit 3: how many old passwords the system remembers
Password history is the number of earlier passwords the system keeps on record. Okta's page gives the range for its history setting: "You can configure this setting from one to 30 passwords." Okta: Configure a password policy
The choice is deliberate.
For Microsoft 365, the page I checked covers expiration only. I cannot compare history limits from a quote, so do not assume Microsoft 365 has the same range as Okta. If password history matters to your firm, check the admin center setting directly, write down the limit you see, and note the date you checked it. A number you wrote down yourself is better than a number you remember from a different product.
Okta's page also says, "You can configure this setting for up to 9,999 minutes." Okta: Configure a password policy That line describes a time-based setting that is not one of the three limits in this post, so this post does not explain it. If your firm uses that setting, read the full Okta page before you change it, so you know what it controls.
The three limits side by side
The table below puts the three limits next to each other. Read the cells as the range each official page gives, not as a recommendation.
| Limit | Microsoft 365 | Okta |
|---|---|---|
| Expiration | Expire after 14 to 730 days, or never expire (Microsoft Learn) | Up to 999 days (Okta) |
| Minimum length | Not stated on the page I checked | Four to 30 characters, default eight (Okta) |
| Password history | Not stated on the page I checked | One to 30 passwords (Okta) |
Northfield's choices follow from these ranges. On Microsoft 365 it sets expiry to 730 days, the top of the allowed range. On Okta it sets the longest expiry Okta allows, sets a minimum length above the default of eight, and sets history to 30. Those values are Northfield's choices within the ranges, not requirements from the vendors.
The gaps in the table matter. For the two rows marked as not stated, you need the admin center or the vendor's current documentation before you make a promise to reps. A gap in a comparison is a reason to check, not a reason to assume the setting is missing or that it matches the other product.
Setting the rules before quarter end
Plan the change in order. The steps are simple, but changing several settings at once makes it hard to tell which one caused a problem. Start by confirming that the person making the change holds the user administrator role in Microsoft 365. Microsoft's page says the steps require it, so there is no point in planning a change that the leader cannot carry out. For Okta, confirm which admin role its current documentation requires. For related admin console checks, see Okta admin console session timeout.
Next, write down the current value of every setting you plan to change. Northfield records the expiry, minimum length, and history values before touching anything. If a rule causes trouble, the leader can set the old value back, and nobody has to guess what it was. The written record also helps the next administrator who inherits the tenant.
Then change one platform at a time. Northfield starts with Microsoft 365, because the leader can test the expiry setting on their own account first. After the change, the leader signs in with a test account to check that the new rule behaves as expected. Then Okta gets the same treatment. Doing both platforms on the same afternoon makes it hard to know which change caused a sign-in problem.
Keep the rollback plan simple. A rollback is only useful if someone can carry it out quickly, so the leader should know where each setting lives before the change starts, not while a rep is waiting on a sign-in. Restoring a recorded value is usually faster than working out a problem on the fly.
Timing matters as well. Northfield avoids making changes in the final days of the quarter, because those days coincide with deal reviews and the most sensitive customer work. It makes the change early, lets a few working days pass, and fixes anything that came up before the team's busiest stretch. A change made in a rush is harder to test and harder to roll back.
Finally, tell reps what is changing, when it takes effect, and who to contact if they get locked out. A short written note works best. It should name the new rule in plain words, explain that existing passwords stay the same until a rep changes them, and give a single person to call. Reps who know the rule before it applies are less likely to be surprised by a prompt in the middle of a call.
Helping reps keep up with the rules
A rule only works if reps can follow it. A frequent failure in a small team is not a weak setting. It is a rep who writes a long password on a sticky note because the rule is hard to live with. Northfield tries to remove that pressure by making the approved path easy, rather than by adding more rules.
The approved path is a password manager. The NCSC quote in the length section makes the case: one strong primary password, with the manager handling the rest. Northfield picks one manager for the whole team, so the firm can support it, and it asks reps not to store passwords in shared documents, chat messages, or spreadsheets. A shared document is a common place for a password to be copied and then forgotten.
Northfield also runs a short setup session. The leader spends a few minutes on a call showing each rep how to create an entry, generate a long password, and sign in with it. Reps who try it once with someone next to them are much more likely to keep using it. A written version of the same steps helps for the reps who could not attend.
Expect questions in the first week. Some reps will ask why a password expires at all, and some will ask why a new password cannot match an old one. Answer them directly and point back to the rule. If a rep reports a lockout, the leader should check the account's sign-in activity in the admin center for your platform, confirm the account is in the right state, and then help the rep through the reset. Keep those answers consistent, because mixed answers from different people make the rule seem optional.
What to do next
Write down the three limits you plan to use, the value you chose for each, and the page you checked to confirm it. For Microsoft 365, that means the expiry range from the Microsoft page and an admin center check for length and history. For Okta, that means the ranges on the Okta page and the values you set. Keep that note with the tenant settings so the next person can see what was chosen and why.
Then make the change early, test it on one account, and tell reps in plain words what is changing and when. The quarter is busy enough without a password problem landing in the middle of it. A small, well-documented change made a few weeks ahead will do more for the team than a long list of strict rules announced at the last minute.
Frequently asked questions
Does Microsoft 365 set a minimum password length?
The Microsoft 365 page checked here gives no minimum length range, so check the password settings in your own admin center.
What is the longest password expiry in Okta?
Okta's page says the setting can be configured for up to 999 days. Read that line next to the expiration setting it describes.
What expiry did Northfield choose?
That is a judgment call, and a compliance requirement for a shorter interval overrides it.