starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #5300] [Bug]: Standard Template: Disable Guest accounts that have not logged on for a number of days #2549

New issue

Closed

opened 2026-03-02 13:53:15 +03:00 by kerem · 6 comments

kerem commented

2026-03-02 13:53:15 +03:00

Owner

Originally created by @NetSolEL on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5300

Required confirmations before submitting

I can reproduce this issue on the latest released versions of both CIPP and CIPP-API.
I have searched existing issues (both open and closed) to avoid duplicates.
I am not requesting general support; this is an actual bug report.

Issue Description

In the standard templates there is a policy called:
Disable Guest accounts that have not logged on for a number of days
The requested value for this policy is 90 days.
We have remediated this policy for our tenants.
It seems, that this policy was updated somewhen yesterday, January 29, as it started disabling guest accounts yesterday around 9pm local time (GMT+1), with interactive sign-in dates prior the 90 days. Until then, this policy also checked the non-interactive sign-ins.
Since yesterday, it only refers to the interactive sign-in date, which is usually older and sometimes exceeds the 90 days, although there are non-interactive sign-ins a few days ago.
We believe, this policy should check both sign-in types (interactive and non-interactive) and only disable accounts, where both dates are older than 90 days.

Directory Audits - rsgroupbiz.onmicrosoft.com.pdf

We have actually set the appropriate policy to "Report" instead of "Remediate", until this is fixed.

Environment Type

Non-sponsored user

Front End Version

v10.0.6

Back End Version

v10.0.7

Relevant Logs / Stack Trace

Originally created by @NetSolEL on GitHub (Jan 30, 2026). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5300 ### Required confirmations before submitting - [x] **I can reproduce this issue on the latest released versions** of both CIPP and CIPP-API. - [x] **I have searched existing issues** (both open and closed) to avoid duplicates. - [x] I am **not** requesting general support; this is an actual bug report. ### Issue Description In the standard templates there is a policy called: Disable Guest accounts that have not logged on for a number of days The requested value for this policy is 90 days. We have remediated this policy for our tenants. It seems, that this policy was updated somewhen yesterday, January 29, as it started disabling guest accounts yesterday around 9pm local time (GMT+1), with interactive sign-in dates prior the 90 days. Until then, this policy also checked the non-interactive sign-ins. Since yesterday, it only refers to the interactive sign-in date, which is usually older and sometimes exceeds the 90 days, although there are non-interactive sign-ins a few days ago. We believe, this policy should check both sign-in types (interactive and non-interactive) and only disable accounts, where both dates are older than 90 days. [Directory Audits - rsgroupbiz.onmicrosoft.com.pdf](https://github.com/user-attachments/files/24967721/Directory.Audits.-.rsgroupbiz.onmicrosoft.com.pdf) We have actually set the appropriate policy to "Report" instead of "Remediate", until this is fixed. ### Environment Type Non-sponsored user ### Front End Version v10.0.6 ### Back End Version v10.0.7 ### Relevant Logs / Stack Trace ```plaintext ```

kerem

2026-03-02 13:53:15 +03:00

closed this issue
added the
bug

Sponsor Priority

unconfirmed-by-user

not-assigned
labels

kerem commented

2026-03-02 13:53:16 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 30, 2026):

Thank you for reporting a potential bug. If you would like to work on this bug, please comment:

I would like to work on this please!

Thank you for helping us maintain the project!

@github-actions[bot] commented on GitHub (Jan 30, 2026): Thank you for reporting a potential bug. If you would like to work on this bug, please comment: > I would like to work on this please! Thank you for helping us maintain the project!

kerem commented

2026-03-02 13:53:16 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Jan 30, 2026):

Update to the latest version.

@KelvinTegelaar commented on GitHub (Jan 30, 2026): Update to the latest version.

kerem commented

2026-03-02 13:53:16 +03:00

Author

Owner

@NetSolEL commented on GitHub (Jan 30, 2026):

Here is an example of a guest account, that was disabled by this policy, due to the interactive sign-in date:

But the non-interactive sign-in date is from yesterday and this guest account actively used his account, as I checked with him.

@NetSolEL commented on GitHub (Jan 30, 2026): Here is an example of a guest account, that was disabled by this policy, due to the interactive sign-in date: <img width="856" height="558" alt="Image" src="https://github.com/user-attachments/assets/a2ebf1e9-8934-4d5f-bf94-1dac4dc4634c" /> But the non-interactive sign-in date is from yesterday and this guest account actively used his account, as I checked with him.

kerem commented

2026-03-02 13:53:16 +03:00

Author

Owner

@NetSolEL commented on GitHub (Jan 30, 2026):

Update to the latest version.

There is no update, when I check for it:

@NetSolEL commented on GitHub (Jan 30, 2026): > Update to the latest version. There is no update, when I check for it: <img width="273" height="272" alt="Image" src="https://github.com/user-attachments/assets/243bf76b-6369-44d3-b0ed-ff50b08ef026" />

kerem commented

2026-03-02 13:53:16 +03:00

Author

Owner

@inventitinkoop commented on GitHub (Jan 30, 2026):

Same issue here. Also no update available. We are running on 10.0.6

@inventitinkoop commented on GitHub (Jan 30, 2026): Same issue here. Also no update available. We are running on 10.0.6

kerem commented

2026-03-02 13:53:16 +03:00

Author

Owner

@kris6673 commented on GitHub (Jan 30, 2026):

Same issue here. Also no update available. We are running on 10.0.6

It was fixed in v10.0.7 of the backend. You can run this script to fix it: https://discord.com/channels/905453405936447518/1199069319850639410/1466748257211252827
or
https://gist.github.com/kris6673/bbbca0768ccce1e6960f6e51457987d0

@kris6673 commented on GitHub (Jan 30, 2026): > Same issue here. Also no update available. We are running on 10.0.6 It was fixed in v10.0.7 of the backend. You can run this script to fix it: https://discord.com/channels/905453405936447518/1199069319850639410/1466748257211252827 or https://gist.github.com/kris6673/bbbca0768ccce1e6960f6e51457987d0

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#2549

No description provided.

Rows
Columns