WEBVTT

00:00:00.030 --> 00:00:04.180 position:50% align:center size:88%
Let’s review the recorded rollback of an
isolated Azure change.

00:00:04.230 --> 00:00:08.243 position:50% align:center size:88%
We’ll distinguish restored test exposure
from a safe final baseline.

00:00:08.723 --> 00:00:11.723 position:50% align:center size:88%
This change was rolled back on the eighth
of October.

00:00:11.773 --> 00:00:15.048 position:50% align:center size:88%
We are reading that history through the
current interface.

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

00:00:18.423 --> 00:00:22.048 position:50% align:center size:88%
This review performs no new rollback or
cloud write.

00:00:22.098 --> 00:00:24.489 position:50% align:center size:88%
The later cleanup is a separate part of
the record.

00:00:26.560 --> 00:00:30.435 position:50% align:center size:88%
The Verification section records the
earlier forward fix.

00:00:30.510 --> 00:00:34.085 position:50% align:center size:88%
The rule deletion was followed by a
cleared control check.

00:00:34.160 --> 00:00:37.710 position:50% align:center size:88%
That result came before the rollback
restored the captured rule.

00:00:37.785 --> 00:00:41.010 position:50% align:center size:88%
Keep the forward verdict separate from the
restoration read.

00:00:41.110 --> 00:00:44.672 position:50% align:center size:88%
Neither is a fresh resource check
performed by this review.

00:00:46.600 --> 00:00:50.800 position:50% align:center size:88%
What ran identifies the forward operation
and its revision.

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

00:00:54.525 --> 00:00:58.375 position:50% align:center size:88%
The retained write connection belonged to
that approved operation.

00:00:58.425 --> 00:01:01.550 position:50% align:center size:88%
The resource identity is masked in this
review.

00:01:01.650 --> 00:01:05.203 position:50% align:center size:88%
Reading this record grants no permission
to execute it again.

00:01:07.240 --> 00:01:11.090 position:50% align:center size:88%
Open the captured before-state artifact
from the Safety net.

00:01:11.165 --> 00:01:15.265 position:50% align:center size:88%
The inverse restores the rule captured
before the forward deletion.

00:01:15.340 --> 00:01:18.740 position:50% align:center size:88%
That was the deliberately introduced trial
condition.

00:01:18.815 --> 00:01:22.140 position:50% align:center size:88%
It was not the empty baseline from before
the exercise.

00:01:22.215 --> 00:01:25.651 position:50% align:center size:88%
Return to the change to read its separate
restoration result.

00:01:27.480 --> 00:01:31.505 position:50% align:center size:88%
The Safety net records the compiled
rollback and its result.

00:01:31.580 --> 00:01:35.755 position:50% align:center size:88%
The restoration read confirmed the
captured configuration returned.

00:01:35.830 --> 00:01:39.505 position:50% align:center size:88%
Restored exposure does not mean safe
production recovery.

00:01:39.580 --> 00:01:43.080 position:50% align:center size:88%
The temporary rule was then removed in a
separate cleanup.

00:01:43.155 --> 00:01:47.533 position:50% align:center size:88%
The saved cleanup receipt confirms the
empty, unattached baseline.

00:01:49.240 --> 00:01:52.815 position:50% align:center size:88%
The linked incident retains the earlier
validation verdict.

00:01:52.915 --> 00:01:56.840 position:50% align:center size:88%
Read its time alongside the change and
restoration evidence.

00:01:56.940 --> 00:02:01.265 position:50% align:center size:88%
This was a manually released rollback,
recorded on October eighth.

00:02:01.340 --> 00:02:05.640 position:50% align:center size:88%
The failed-change recovery sweep was not
exercised by that take.

00:02:05.740 --> 00:02:09.613 position:50% align:center size:88%
Final cleanup was checked separately; no
new recovery is claimed.