This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 32%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
When I create a new Auto-labeling in Purview Information Protection, the simulation mode appears "Expired". It does not perform the simulation. If the simulation is restarted, it does not even try to simulate. Does anyone know why this happens?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 38%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Maite Reina Did you try to re-create the Policy?
https://learn.microsoft.com/en-us/purview/dlp-simulation-mode-learn#simulation-overview
Yes, more than twice. Result: Status Expired. No simulations, no scans, nothing. Before that, February 15 2024, i did the last Simulation, but after that, nothing. I was tryed with diferent tenants and the result is the same: date of simulation Expired.
@Maite Reina This may need deeper investigation, do you have a support plan, where you can contact the Technical Support team? if not, then please let me know and we can help with one-time support ticket.
Yes, I contacted the technical support, but they are still investigating it and no one gives me an answer, I will contact them again, if today I have no answer, I will give you the case number, is that okay?
Maite Reina Thanks for the information, Sure please keep us posted.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 20%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFC%3C/text%3E%3C/svg%3E)
@Anonymous I also encountered the same problem as you. Is there any reply from Microsoft?
Yes, I get a response from the technician saying: The problem seemed to be an internal degradation of the system, not only of its organization.
Now it is working. Badly but it works :)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 63%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAJ%3C/text%3E%3C/svg%3E)
I encountered the same problem too. Is there anything we can do to resolve the issue?
Hi, I encountered the same issue. Is there anything that we can do on our side?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 64%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGL%3C/text%3E%3C/svg%3E)
I have the same problem. MS technical support has not replied for more than a month. Apparently it was normal until February 7, 2024, but I haven't heard back for a month. It's the same even if I test multiple tenants, isn't that a bug?