Menghua Chen (MSFT)
Menghua Chen (MSFT)
@jairmyree Your PR[#34608](https://github.com/Azure/azure-sdk-for-java/pull/40368) does not fix the [link2](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/search/azure-search-documents/src/samples/java/com/azure/search/documents/SearchJavaDocCodeSnippets.java#L1154) part in issue2. I have created a PR https://github.com/Azure/azure-sdk-for-java/pull/40355 to fix this issue. Can you please review and approve it? 
@vjmanda We will replace `infra/core` with `avm` for azd. The current module is missing feature [azurerm_key_vault_access_policy](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/key_vault_access_policy). Can we choose to add [azurerm_key_vault_access_policy](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/key_vault_access_policy) to support [Access Policy Entry](https://learn.microsoft.com/en-us/rest/api/keyvault/keyvault/vaults/update-access-policy?view=rest-keyvault-keyvault-2022-07-01&tabs=HTTP#accesspolicyentry)? @jongio for notification.
In the latest round of testing, the issue no longer exists.
In the latest round of testing, the issue no longer exists.
@bradygaster According to the latest code and azd version test, this issue can no longer be reproduced, thank you.
In the usage scenario in https://github.com/Azure/azure-dev/issues/4593, the main.bicepparam environment variables being evaluated too early will cause the input parameters during deployment to be inconsistent with the actual environment.
@rajeshkamal5050 In the latest round of Aspire testing, this issue was encountered. **Repro Steps:** 1. Clone [aspire-samples](https://github.com/dotnet/aspire-samples). 2. Run command `azd config set alpha.azd.operations on`. 3. Run command `cd samples/Metrics`....
@rajeshkamal5050 In the latest round of Aspire testing, this issue was encountered. **Repro Steps:** 1. Clone [aspire-samples](https://github.com/dotnet/aspire-samples). 2. Run command `azd config set alpha.azd.operations on`. 3. Run command `cd samples/Metrics`....
@rajeshkamal5050 and @vhvb1989 Based on the latest code test, it works fine on the C drive in Windows but encounters the following error on the **D** drive:  **Repro Steps:**...
@vhvb1989 Based on the latest code test, this issue has been fixed.😄