Skip to content

Repo sync for protected branch #10514

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Dec 2, 2024
16 changes: 16 additions & 0 deletions docs/azure/how-to-sign-in-with-azure-subscription.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,10 +39,26 @@ Visual Studio allows you to sign in with multiple accounts and it let's you work

To avoid having to sign in when you connect to an Azure service or publish to Azure, you can use Visual Studio's account management features to add your Azure subscription to your Visual Studio accounts. In that case, you are automatically signed in whenever you're using Visual Studio. See [Add and switch user accounts to Visual Studio](../ide/signing-in-to-visual-studio.md#add-and-switch-user-accounts-in-visual-studio).

> [!NOTE]
> If you have a personal and a work (or school) account, that are both owners on the same subscription, you might encounter a situation where the personal account doesn't get the expected role-based permissions on a service dependency, such as a storage account, but the work account does. The indication that this issue is happening is a timeout in the Connected Services summary screen:
>
>`Create Azure Resource Connector Service result: Succeeded. resourceid: <resourceid> Error code: MaxWaitingTimeHit. Error message: Max running time hit when operating service connector resource.`
>
> To get around this, manually add the required roles for the personal account in the [Azure portal](https://portal.azure.com).

:::moniker range=">=vs-2022"

## Filter multiple tenants

If you have multiple tenants, you can filter them, so that you only see the Azure resources relevant to your current work. See [Opt out of a specific Microsoft Entra tenant in Visual Studio](../ide/work-with-multi-factor-authentication.md#how-to-opt-out-of-using-a-specific-microsoft-entra-tenant-in-visual-studio).

## Tokens and chained credentials

Visual Studio 2022 uses security tokens to authenticate to Azure services in most cases. The underlying API used is the
[Microsoft Authentication Library (MSAL)](/entra/identity-platform/msal-overview). On the same machine, you might also use other ways to sign in to Azure, for example, `az login` from the Azure CLI, or through Visual Studio Code. These methods of authentication are designed to work together as a set of chained credentials. For example, in cases where a client application uses an API like <xref:Azure.Identity.DefaultAzureCredential> to authenticate to Azure on your development machine, there's a well-defined sequence in which credentials in the chain are attempted. For more information, see [Credential chains in the Azure Identity Library for .NET](/dotnet/azure/sdk/authentication/credential-chains?tabs=dac).

:::moniker-end

## Related content

- [Access multiple user accounts](../ide/sign-in-access-multiple-accounts.md)
Expand Down
1 change: 1 addition & 0 deletions docs/msbuild/assignculture-task.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ The following table describes the parameters of the `AssignCulture` task.
|`AssignedFilesWithNoCulture`|Optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` output parameter.<br /><br /> Contains the subset of the items from the `AssignedFiles` parameter that don't have a `Culture` metadata entry.|
|`CultureNeutralAssignedFiles`|Optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` output parameter.<br /><br /> Contains the same list of items that is produced in the `AssignedFiles` parameter, except with the culture removed from the file name.<br /><br /> The task only removes the culture from the file name if it's a valid culture identifier.|
|`Files`|Required <xref:Microsoft.Build.Framework.ITaskItem>`[]` parameter.<br /><br /> Specifies the list of files with embedded culture names to assign a culture to. The task tries to figure out if each file is a culture-specific resource, and if so, what culture. To skip this detection process and force a file to be culture-neutral, set the metadata entry `WithCulture` to `false`.|
|`RespectAlreadyAssignedItemCulture`|Optional `bool` parameter.<br /><br /> If set to `true` - the already set Culture metadata on the `Files` item parameter is respected and the `CultureNeutralAssignedFiles` will be populated with unchanged filename from `Files`.|

## Remarks

Expand Down