Skip to content

Commit 729c580

Browse files
Merge pull request #297187 from MicrosoftDocs/main
Merged by Learn.Build PR Management system
2 parents 4b8d88d + 2725cf3 commit 729c580

30 files changed

+143
-126
lines changed

articles/analysis-services/analysis-services-manage-users.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,9 @@ Power BI Desktop, Visual Studio, and SSMS support Active Directory Universal Aut
3131

3232
If signing in to Azure by using a Windows account, and Universal Authentication is not selected or available (Excel), [Active Directory Federation Services (AD FS)](/windows-server/identity/ad-fs/deployment/how-to-connect-fed-azure-adfs) is required. With Federation, Microsoft Entra ID and Microsoft 365 users are authenticated using on-premises credentials and can access Azure resources.
3333

34+
> [!NOTE]
35+
> When creating a token with custom logic, it must either be a user token or an application service principal and the audience must be set to exactly `https://*.asazure.windows.net`
36+
3437
### SQL Server Management Studio (SSMS)
3538

3639
Azure Analysis Services servers support connections from [SSMS V17.1](/sql/ssms/download-sql-server-management-studio-ssms) and higher by using Windows Authentication, Active Directory Password Authentication, and Active Directory Universal Authentication. In general, it's recommended you use Active Directory Universal Authentication because:

articles/cloud-services-extended-support/feature-support-analysis.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This article provides a feature analysis of Cloud Services (extended support) an
1818
| Feature | CSES | Virtual Machine Scale Sets (Flex) | Virtual Machine Scale Sets (Uniform) |
1919
|---|---|---|---|
2020
|Virtual machine type|Basic Azure PaaS VM (Microsoft.compute/cloudServices)|Standard Azure IaaS VM (Microsoft.compute/virtualmachines)|Scale Set specific VMs (Microsoft.compute /virtualmachinescalesets/virtualmachines)|
21-
|Maximum Instance Count (with FD guarantees)|1100|1000|3000 (1000 per Availability Zone)|
21+
|Maximum Instance Count (with FD guarantees)|1100 subject to capacity and load balancer support|1000|3000 (1000 per Availability Zone)|
2222
|SKUs supported|D, Dv2, Dv3, Dav4 series, Ev3, Eav4 series, G series, H series|D series, E series, F series, A series, B series, Intel, AMD; Specialty SKUs (G, H, L, M, N) aren't supported|All SKUs|
2323
|Full control over VM, NICs, Disks|Limited control over NICs and VM via CS-ES APIs. No support for Disks|Yes|Limited control with virtual machine scale sets VM API|
2424
|RBAC Permissions Required|Compute Virtual Machine Scale Sets Write, Compute VM Write, Network|Compute Virtual Machine Scale Sets Write, Compute VM Write, Network|Compute Virtual Machine Scale Sets Write|

articles/connectors/introduction.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,7 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: conceptual
8-
ms.date: 09/06/2024
9-
ms.custom: engagement-fy23
8+
ms.date: 03/27/2025
109
# Customer intent: As a developer, I want to learn how connectors help me access data, events, and resources in other apps, services, systems, and platforms from my workflow in Azure Logic Apps.
1110
---
1211

@@ -33,11 +32,11 @@ In Azure Logic Apps, connectors are either *built in* or *managed*. Some connect
3332

3433
* [Built-in connectors](built-in.md) are designed to run directly and natively inside Azure Logic Apps.
3534

36-
* [Managed connectors](managed.md) are deployed, hosted, and managed in Azure by Microsoft. Managed connectors mostly provide a proxy or a wrapper around an API that the underlying service or system uses to communicate with Azure Logic Apps.
35+
In the designer, all built-in connectors appear in the connector gallery within the **In app** group.
3736

38-
* In a Consumption workflow, managed connectors appear in the designer under the **Standard** or **Enterprise** labels, based on their pricing level.
37+
* [Managed connectors](managed.md) are deployed, hosted, and managed in Azure by Microsoft. Managed connectors mostly provide a proxy or a wrapper around an API that the underlying service or system uses to communicate with Azure Logic Apps.
3938

40-
* In a Standard workflow, all managed connectors appear in the designer under the **Azure** label.
39+
In the designer, all managed connectors appear in the connector gallery within the **Shared** group. They are billed at either the **Standard** or **Enterprise** level.
4140

4241
For more information, see the following documentation:
4342

articles/devtest-labs/devtest-lab-add-vm.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,7 @@ This article describes how to create Azure virtual machines (VMs) in Azure DevTe
4141
>[!NOTE]
4242
>If you enable hibernation, you must also select **Public IP** in **Advanced Settings**. **Private** and **Shared** IPs aren't supported if hibernation is enabled.
4343
- **OS disk type**: Keep the default value for the base, or select a different option from the dropdown list.
44+
- **Security type**: You can select **Trusted launch** to enable trusted launch for Generation 2 VMs. If you select **Trusted launch**, select the **Enable secure boot**, **Enable vTPM**, and **Integrity monitoring** checkboxes as needed. For more information, see [Trusted Launch for Azure virtual machines](/azure/virtual-machines/trusted-launch).
4445
- **Artifacts**: Optionally, select **Add or Remove Artifacts** to select and configure artifacts to add to the VM. For instructions, see [Add artifacts](#add-artifacts).
4546

4647
:::image type="content" source="./media/devtest-lab-add-vm/portal-lab-vm-basic-settings.png" alt-text="Screenshot that shows the VM Basic Settings page.":::
3.92 KB
Loading

articles/governance/policy/troubleshoot/general.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -357,6 +357,15 @@ In the prior event, the error case can be monitored from the [admission webhook
357357

358358
Regardless of the scenario, Azure policy retains the last known policy on the cluster and keeps the guardrails in place.
359359

360+
### Scenario: The regex I provided in my policy assignment isn't matching the resources I expected it to match
361+
362+
#### Cause
363+
The `regex.match` function in rego uses RE2, which is not the default flavor served by many online regex matchers. If you are testing your regex in an online matcher, you may see different results from what will be evaluated on the cluster.
364+
365+
#### Resolution
366+
367+
You will need to select the RE2 or golang flavor of regex in your matcher. See [the rego docs](https://docs.styra.com/opa/rego-by-example/builtins/regex/match) for more details on the RE2 flavor and what online tooling is recommended to test your regex.
368+
360369
## Next steps
361370

362371
If your problem isn't listed in this article or you can't resolve it, get support by visiting one of the following channels:

articles/iot-operations/troubleshoot/known-issues.md

Lines changed: 1 addition & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -15,22 +15,6 @@ This article lists the current known issues for Azure IoT Operations.
1515

1616
This section lists current known issues that might occur when you deploy, update, or uninstall Azure IoT Operations.
1717

18-
### Unable to retrieve some image pull secrets
19-
20-
---
21-
22-
Issue ID: 8959
23-
24-
---
25-
26-
Log signature: `"Unable to retrieve some image pull secrets (regcred)"`
27-
28-
---
29-
30-
During and after deploying Azure IoT Operations, you might see warnings about `Unable to retrieve some image pull secrets (regcred)` in the logs and Kubernetes events. These warnings are expected and don't affect the deployment and use of Azure IoT Operations.
31-
32-
No workaround needed.
33-
3418
### Error creating custom resources
3519

3620
---
@@ -67,7 +51,7 @@ Currently, there's no workaround for the issue. If you need a cluster that suppo
6751

6852
---
6953

70-
Issue ID: 0000
54+
Issue ID: 9928
7155

7256
---
7357

articles/logic-apps/block-connections-across-tenants.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: how-to
8-
ms.date: 03/15/2024
8+
ms.date: 03/27/2025
99
# Customer intent: As a developer, I want to prevent access to and from other Microsoft Entra tenants.
1010
---
1111

articles/logic-apps/create-single-tenant-workflows-templates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: how-to
8-
ms.date: 08/23/2024
8+
ms.date: 03/27/2025
99
# Customer intent: As a developer, I want to use a template as a faster way to build my Standard logic app workflow that runs in single-tenant Azure Logic Apps.
1010
---
1111

articles/logic-apps/index.yml

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ metadata:
1010
ms.topic: landing-page
1111
author: ecfan
1212
ms.author: estfan
13-
ms.date: 08/23/2024
13+
ms.date: 03/27/2025
1414

1515
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
1616

@@ -64,6 +64,10 @@ landingContent:
6464
url: create-single-tenant-workflows-azure-portal.md
6565
- text: Create Standard workflow from template - Portal
6666
url: create-single-tenant-workflows-templates.md
67+
- text: Create Consumption workflows with Visual Studio Code
68+
url: quickstart-create-logic-apps-visual-studio-code.md
69+
- text: Create Standard workflows with Visual Studio Code
70+
url: create-standard-workflows-Visual-Studio-Code.md
6771
- linkListType: tutorial
6872
links:
6973
- text: Create a schedule-based workflow
@@ -97,8 +101,8 @@ landingContent:
97101
linkLists:
98102
- linkListType: how-to-guide
99103
links:
100-
- text: Manage logic apps - Visual Studio
101-
url: manage-logic-apps-with-visual-studio.md
104+
- text: Manage logic apps - Visual Studio Code
105+
url: manage-logic-apps-visual-studio-code.md
102106
- text: Secure access and data
103107
url: logic-apps-securing-a-logic-app.md
104108
- text: Authenticate with managed identities

0 commit comments

Comments
 (0)