eDiscovery Purge
I am attempting to use the eDiscovery Purge feature documented here: ediscoverySearch: purgeData. My goal is to delete Team messages exactly as described. However, I have not had any success getting any indication that it is working. The is a lot of setup required to complete before initiating the purge activity. That has all been done.
I have attempted this through PowerShell, Graph Explorer, and REST requests in two scenarios, 1) without body parameters in the request, and 2) with body parameters in the request.
Scenario 1)
POST /v1.0/security/cases/ediscoveryCases/<case_id>/searches/<search_id>/purgeData
Request is accepted with 202. The job completes within Purview, but no data is deleted.
Scenario 2)
POST /v1.0/security/cases/ediscoveryCases/<case_id>/searches/<search_id>/purgeData
Request is NOT accepted with 400, bad request. The parameters are documented in the link but they are no accepted. That said, I can sent any other meaningless parameters, and the request will be accepted. As long as I don’t include the purgeType or purgeArea in the request.
Has anyone had any success with this API call?
I am attempting to use the eDiscovery Purge feature documented here: ediscoverySearch: purgeData. My goal is to delete Team messages exactly as described. However, I have not had any success getting any indication that it is working. The is a lot of setup required to complete before initiating the purge activity. That has all been done. I have attempted this through PowerShell, Graph Explorer, and REST requests in two scenarios, 1) without body parameters in the request, and 2) with body parameters in the request. Scenario 1)POST /v1.0/security/cases/ediscoveryCases/<case_id>/searches/<search_id>/purgeDataRequest is accepted with 202. The job completes within Purview, but no data is deleted. Scenario 2)POST /v1.0/security/cases/ediscoveryCases/<case_id>/searches/<search_id>/purgeData{ “purgeType” : “permanentlydeleted”, “purgeArea” : “teamsMessages”}Request is NOT accepted with 400, bad request. The parameters are documented in the link but they are no accepted. That said, I can sent any other meaningless parameters, and the request will be accepted. As long as I don’t include the purgeType or purgeArea in the request. Has anyone had any success with this API call? Read More