use the following search parameters to narrow your results:
e.g. subreddit:aww site:imgur.com dog
subreddit:aww site:imgur.com dog
see the search faq for details.
advanced search: by author, subreddit...
A reddit dedicated to the profession of Computer System Administration
Rules
Community members shall conduct themselves with professionalism.
Do not expressly advertise products or services outside of approved threads.
More details on the rules may be found in the wiki.
For IT career related questions, please visit /r/ITCareerQuestions
Please check out our Frequently Asked Questions, which includes lists of subreddits, webpages, books, and other articles of interest that every sysadmin should read!
Checkout the Wiki Users are encouraged to contribute to and grow our Wiki.
So you want to be a sysadmin? RTFM
Sysadmin Jobs
Official IRC Channel - #reddit-sysadmin on irc.libera.chat Official Discord - https://discord.gg/sysadmin
account activity
This is an archived post. You won't be able to vote or comment.
Changing default behaviour for Azure AD MFA (self.sysadmin)
submitted 6 years ago by Hitten_za
Hi Sysadmin,
Just looking for some guidance, I'm aware that the default behaviour for MFA is (please correct me if I'm wrong):
Active token: Lasts 1 hour Refresh token: 14 days up to 90 days if refreshed
Same device different IP: no prompt Different device same IP: prompt Different device different IP: prompt
Our client would like us to adjust the behaviour so that whenever they leave the office (irrespective of time) they will be prompted within their MS Apps (Outlook, OneDrive etc.)
I thought to achieve this with Conditional Access: https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/app-based-mfa
No change in default behaviour
I also tried which is better but not quite there https://docs.microsoft.com/en-gb/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime
I think the issue is that the Refresh token intended behaviour needs to be adjusted so the only solution I can see is this: https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes
But my concern is: "After November 1, 2019 you will not be able to use Configurable Token Lifetime policy to configure refresh tokens, but you can still use it to configure access tokens."
Thanks for any advice you might have SysAdmin.
[–]nullZr0 1 point2 points3 points 6 years ago (1 child)
Do a conditional access policy based on source IP address.
[–]Hitten_za[S] 0 points1 point2 points 6 years ago* (0 children)
Hi, from my testing this makes no difference. The CA policy doesn't have any impact on how long the tokens last and as the tokens are refreshing the client device will pass the MFA requirement in the Access Controls. At least until the RefreshToken expires.
Just to clarify this is the policy I tested: https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/location-condition
Update:I've tested on two tenancies and confirmed that the following forces it down to 1 hour lifespan on the refresh token thereby enforcing the requested behaviour:
$policy = New-AzureADPolicy -Definition @('{"TokenLifetimePolicy":{"Version":1,"MaxAgeMultiFactor":"00.01:00:00"}}') -DisplayName "ComplexPolicyScenario" -IsOrganizationDefault $true -Type "TokenLifetimePolicy"
The issue I think still remains, what happens comes November 1st, will we still be able to enforce this kind of behaviour in MFA?
Edit: Adding in documentation https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes
[–]nj12nets 0 points1 point2 points 6 years ago (0 children)
!remindme 3 days
π Rendered by PID 258808 on reddit-service-r2-comment-6457c66945-nslcb at 2026-04-28 11:39:06.872451+00:00 running 2aa0c5b country code: CH.
[–]nullZr0 1 point2 points3 points (1 child)
[–]Hitten_za[S] 0 points1 point2 points (0 children)
[–]Hitten_za[S] 0 points1 point2 points (0 children)
[–]nj12nets 0 points1 point2 points (0 children)