WEBVTT

00:00:00.030 --> 00:00:03.930 position:50% align:center size:88%
Let’s review a verified cloud fix and its
later rollback.

00:00:03.980 --> 00:00:07.710 position:50% align:center size:88%
We’ll follow the recorded evidence without
executing another change.

00:00:08.190 --> 00:00:11.765 position:50% align:center size:88%
This trial change was executed on the
eighth of October.

00:00:11.840 --> 00:00:14.215 position:50% align:center size:88%
Its current status is rolled back.

00:00:14.290 --> 00:00:18.315 position:50% align:center size:88%
That later state does not erase the
earlier forward verification.

00:00:18.390 --> 00:00:21.540 position:50% align:center size:88%
The target was an unattached trial network
group.

00:00:21.590 --> 00:00:24.318 position:50% align:center size:88%
We will read the separate records in their
original order.

00:00:26.320 --> 00:00:28.945 position:50% align:center size:88%
Scroll to the forward verification record.

00:00:29.020 --> 00:00:32.120 position:50% align:center size:88%
The receipt records the successful rule
deletion.

00:00:32.195 --> 00:00:35.595 position:50% align:center size:88%
The control recheck then recorded a
cleared result.

00:00:35.670 --> 00:00:39.345 position:50% align:center size:88%
That result belongs to the forward fix,
before the rollback.

00:00:39.420 --> 00:00:42.299 position:50% align:center size:88%
It is not a fresh assessment performed by
this review.

00:00:44.040 --> 00:00:47.565 position:50% align:center size:88%
Read What ran to inspect the executed
operation.

00:00:47.640 --> 00:00:51.215 position:50% align:center size:88%
It deleted one exact Azure network
security rule.

00:00:51.290 --> 00:00:54.815 position:50% align:center size:88%
The record retains its write connection
and revision.

00:00:54.890 --> 00:00:58.115 position:50% align:center size:88%
The resource identity is masked for this
recording.

00:00:58.165 --> 00:01:01.235 position:50% align:center size:88%
The prepared approval applied to this
specific operation.

00:01:03.280 --> 00:01:06.405 position:50% align:center size:88%
Open the snapshot artifact from the Safety
net.

00:01:06.505 --> 00:01:09.530 position:50% align:center size:88%
This is the rule captured before the
forward write.

00:01:09.580 --> 00:01:12.755 position:50% align:center size:88%
The capture records the temporary trial
condition.

00:01:12.830 --> 00:01:17.355 position:50% align:center size:88%
It is evidence of the previous
configuration, not proof it was safe.

00:01:17.430 --> 00:01:20.475 position:50% align:center size:88%
Return to the change record after
reviewing its provenance.

00:01:22.520 --> 00:01:26.070 position:50% align:center size:88%
The same change also records a compiled
rollback.

00:01:26.145 --> 00:01:30.445 position:50% align:center size:88%
Its restoration read confirmed the
captured configuration returned.

00:01:30.520 --> 00:01:33.770 position:50% align:center size:88%
The trial rule was then removed in
separate cleanup.

00:01:33.820 --> 00:01:38.095 position:50% align:center size:88%
The original empty and unattached baseline
was checked off camera.

00:01:38.195 --> 00:01:42.019 position:50% align:center size:88%
This review does not perform another
rollback or another fix.

00:01:43.920 --> 00:01:47.320 position:50% align:center size:88%
Open the linked incident and its
Validation section.

00:01:47.420 --> 00:01:50.670 position:50% align:center size:88%
Read the recorded verdict together with
its check time.

00:01:50.745 --> 00:01:53.845 position:50% align:center size:88%
The report retains the attempt and its
outcome.

00:01:53.920 --> 00:01:58.370 position:50% align:center size:88%
Keep forward verification, rollback and
final cleanup distinct.

00:01:58.445 --> 00:02:01.541 position:50% align:center size:88%
That chronology is the evidence behind the
recorded fix.