Requesting improved drift functionality. In a scenario where you have a solution baseline and you accepted the drift of a setting for some customers. When you create, let's say, a new solution baseline that is more secure or slighty different, you dont' want to alter the existing solution baseline, you want a new one. If you assign that baseline, it should detect any existing drifts, and have them stay sticky or persist even on new solution baseline assignment. Drift persistense, sticky drift acceptance. The accepted drift should survive new policy assignment, or at least notify you there are existing drifts accepted.
This feature request is in response to this question:
Is it possible to push a policy, then manually edit it on the target tenant, accept the drift, and subsequently push an updated policy with the previously accepted drift to stay aligned?
Comments (1 comment)