> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/es/comandos-de-powershell/remove-psusecretvault.md).

# Remove-PSUSecretVault

Eliminar un registro de bóveda de secretos de PowerShell Universal basado en modelos.

## SINOPSIS

Elimina un registro de bóveda de secretos basado en modelos.

## SINTAXIS

```powershell
Remove-PSUSecretVault -Id <Int64> [<ConnectionOptions>] [<CommonParameters>]
Remove-PSUSecretVault -Name <String> [<ConnectionOptions>] [<CommonParameters>]
Remove-PSUSecretVault -Vault <Vault> [<ConnectionOptions>] [<CommonParameters>]
```

`<ConnectionOptions>`: `[-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]`.

## DESCRIPCIÓN

Quita un registro configurado de almacén de secretos de PowerShell Universal por id., nombre u objeto de almacén de la canalización. Quitar el registro impide que PSU lo utilice; no elimina el Azure Key Vault externo ni purga ningún secreto de Azure.

## EJEMPLOS

```powershell
Remove-PSUSecretVault -Name 'Production Key Vault'
Get-PSUSecretVault -Name 'Production Key Vault' | Remove-PSUSecretVault
```

## PARÁMETROS

| Parámetro                | Descripción                                                                                         |
| ------------------------ | --------------------------------------------------------------------------------------------------- |
| `-Id`                    | Id. de registro numérico obligatorio (conjunto de parámetros Id).                                   |
| `-Name`                  | Nombre de registro obligatorio (conjunto de parámetros Name).                                       |
| `-Vault`                 | Objeto de almacén obligatorio; acepta la entrada de la canalización (conjunto de parámetros Vault). |
| `-ComputerName`          | URL o nombre de host de la API de administración de PSU (alias `-Uri`).                             |
| `-AppToken`              | Token de aplicación de la API de administración.                                                    |
| `-Credential`            | Credenciales de la API de administración.                                                           |
| `-UseDefaultCredentials` | Usa las credenciales actuales de Windows.                                                           |
| `-Integrated`            | Usa el cliente de administración en proceso.                                                        |
| `-TrustCertificate`      | Ignora los errores de validación del certificado.                                                   |
| `-Cookies`               | Reutiliza las cookies de autenticación de la sesión.                                                |

## SALIDAS

Ninguno.

## ENLACES RELACIONADOS

[Get-PSUSecretVault](/powershell-universal/es/comandos-de-powershell/get-psusecretvault.md) · [New-PSUSecretVault](/powershell-universal/es/comandos-de-powershell/new-psusecretvault.md)

## PERMISOS

El token de acceso requiere `platform.vaults/delete` para quitar un registro de almacén de forma remota.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/powershell-universal/es/comandos-de-powershell/remove-psusecretvault.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.