> 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/da/powershell-kommandoer/remove-psusecretvault.md).

# Remove-PSUSecretVault

Fjern en modelbaseret registrering af en hemmelighedsboks i PowerShell Universal.

## Synopsis

Fjerner en modelbaseret registrering af en hemmelighedsboks.

## Syntaks

```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]`.

## Beskrivelse

Fjerner en konfigureret registrering af en PowerShell Universal-hemmelighedsboks efter id, navn eller boksobjekt fra pipelinen. Fjernelse af registreringen betyder, at PSU holder op med at bruge den; den sletter ikke den eksterne Azure Key Vault og rydder ikke nogen Azure-hemmeligheder.

## Eksempler

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

## Parametre

| Parameter                | Beskrivelse                                                            |
| ------------------------ | ---------------------------------------------------------------------- |
| `-Id`                    | Påkrævet numerisk registrerings-id (parametersættet Id).               |
| `-Name`                  | Påkrævet registreringsnavn (parametersættet Name).                     |
| `-Vault`                 | Påkrævet boksobjekt; accepterer pipelineinput (parametersættet Vault). |
| `-ComputerName`          | URL eller værtsnavn for PSU Management API (alias `-Uri`).             |
| `-AppToken`              | App-token til Management API.                                          |
| `-Credential`            | Legitimationsoplysninger til Management API.                           |
| `-UseDefaultCredentials` | Bruger de aktuelle Windows-legitimationsoplysninger.                   |
| `-Integrated`            | Bruger den integrerede administrationsklient i processen.              |
| `-TrustCertificate`      | Ignorerer fejl ved certifikatvalidering.                               |
| `-Cookies`               | Genbruger sessionscookies til godkendelse.                             |

## Output

Ingen.

## Relaterede links

[Get-PSUSecretVault](/powershell-universal/da/powershell-kommandoer/get-psusecretvault.md) · [New-PSUSecretVault](/powershell-universal/da/powershell-kommandoer/new-psusecretvault.md)

## Tilladelser

Adgangstokenet kræver `platform.vaults/delete` for at fjerne en boksregistrering eksternt.


---

# 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/da/powershell-kommandoer/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.