Skip to content

Commit 071208d

Browse files
authored
Merge pull request #235772 from MicrosoftDocs/main
4/25 AM Publish
2 parents 9ff60bf + e48b621 commit 071208d

File tree

147 files changed

+1602
-2182
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

147 files changed

+1602
-2182
lines changed

.openpublishing.redirection.healthcare-apis.json

Lines changed: 36 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -550,33 +550,61 @@
550550
"redirect_document_id": false
551551
},
552552
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-iot-connector-in-azure.md",
553-
"redirect_url": "/azure/healthcare-apis/iot/deploy-new-choose",
553+
"redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
554554
"redirect_document_id": false
555555
},
556556
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-02-new-button.md",
557-
"redirect_url": "/azure/healthcare-apis/iot/deploy-new-button",
557+
"redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
558558
"redirect_document_id": false
559559
},
560560
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-03-new-manual.md",
561-
"redirect_url": "/azure/healthcare-apis/iot/deploy-new-manual",
561+
"redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
562562
"redirect_document_id": false
563563
},
564564
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-05-new-config.md",
565-
"redirect_url": "/azure/healthcare-apis/iot/deploy-new-config",
565+
"redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
566566
"redirect_document_id": false
567567
},
568568
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-06-new-deploy.md",
569-
"redirect_url": "/azure/healthcare-apis/iot/deploy-new-deploy",
569+
"redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
570570
"redirect_document_id": false
571571
},
572572
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-08-new-ps-cli.md",
573-
"redirect_url": "/azure/healthcare-apis/iot/deploy-new-powershell-cli",
573+
"redirect_url": "/azure/healthcare-apis/iot/deploy-json-powershell-cli",
574+
"redirect_document_id": false
575+
},
576+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-arm.md",
577+
"redirect_url": "/azure/healthcare-apis/iot/deploy-arm-template",
574578
"redirect_document_id": false
575579
},
576580
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-bicep-ps-cli.md",
577-
"redirect_url": "/azure/healthcare-apis/iot/deploy-new-bicep-powershell-cli",
581+
"redirect_url": "/azure/healthcare-apis/iot/deploy-bicep-powershell-cli",
578582
"redirect_document_id": false
579-
},
583+
},
584+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-bicep-powershell-cli.md",
585+
"redirect_url": "/azure/healthcare-apis/iot/deploy-bicep-powershell-cli",
586+
"redirect_document_id": false
587+
},
588+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-choose.md",
589+
"redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
590+
"redirect_document_id": false
591+
},
592+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-powershell-cli.md",
593+
"redirect_url": "/azure/healthcare-apis/iot/deploy-json-powershell-cli",
594+
"redirect_document_id": false
595+
},
596+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-config.md",
597+
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-config",
598+
"redirect_document_id": false
599+
},
600+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-deploy.md",
601+
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-post",
602+
"redirect_document_id": false
603+
},
604+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-manual.md",
605+
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-prerequisites",
606+
"redirect_document_id": false
607+
},
580608
{ "source_path_from_root": "/articles/healthcare-apis/iot/iot-connector-overview.md",
581609
"redirect_url": "/azure/healthcare-apis/iot/overview",
582610
"redirect_document_id": false

articles/active-directory/app-provisioning/application-provisioning-log-analytics.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.topic: conceptual
1010
ms.workload: identity
11-
ms.date: 10/06/2022
11+
ms.date: 04/25/2023
1212
ms.author: kenwith
1313
ms.reviewer: arvinh
1414
---
@@ -19,7 +19,7 @@ Provisioning integrates with Azure Monitor logs and Log Analytics. With Azure mo
1919

2020
## Enabling provisioning logs
2121

22-
You should already be familiar with Azure monitoring and Log Analytics. If not, jump over to learn about them and then come back to learn about application provisioning logs. To learn more about Azure monitoring, see [Azure Monitor overview](../../azure-monitor/overview.md). To learn more about Azure Monitor logs and Log Analytics, see [Overview of log queries in Azure Monitor](../../azure-monitor/logs/log-query-overview.md).
22+
You should already be familiar with Azure monitoring and Log Analytics. If not, jump over to learn about them, and then come back to learn about application provisioning logs. To learn more about Azure monitoring, see [Azure Monitor overview](../../azure-monitor/overview.md). To learn more about Azure Monitor logs and Log Analytics, see [Overview of log queries in Azure Monitor](../../azure-monitor/logs/log-query-overview.md).
2323

2424
Once you've configured Azure monitoring, you can enable logs for application provisioning. The option is located on the **Diagnostics settings** page.
2525

@@ -44,7 +44,7 @@ The underlying data stream that Provisioning sends log viewers is almost identic
4444

4545
Azure Monitor workbooks provide a flexible canvas for data analysis. They also provide for the creation of rich visual reports within the Azure portal. To learn more, see [Azure Monitor Workbooks overview](../../azure-monitor/visualize/workbooks-overview.md).
4646

47-
Application provisioning comes with a set of pre-built workbooks. You can find them on the Workbooks page. To view the data, you'll need to ensure that all the filters (timeRange, jobID, appName) are populated. You'll also need to make sure you've provisioned an app, otherwise there won't be any data in the logs.
47+
Application provisioning comes with a set of prebuilt workbooks. You can find them on the Workbooks page. To view the data, ensure that all the filters (timeRange, jobID, appName) are populated. Also confirm the app was provisioned, otherwise there isn't any data in the logs.
4848

4949
:::image type="content" source="media/application-provisioning-log-analytics/workbooks.png" alt-text="Application provisioning workbooks" lightbox="media/application-provisioning-log-analytics/workbooks.png":::
5050

@@ -108,7 +108,7 @@ Alert when there's a spike in disables or deletes.
108108

109109
## Community contributions
110110

111-
We're taking an open source and community-based approach to application provisioning queries and dashboards. If you've built a query, alert, or workbook that you think others would find useful, be sure to publish it to the [AzureMonitorCommunity GitHub repo](https://github.com/microsoft/AzureMonitorCommunity). Then shoot us an email with a link. We'll review and publish it to the service so others can benefit too. You can contact us at [email protected].
111+
We're taking an open source and community-based approach to application provisioning queries and dashboards. Build a query, alert, or workbook that you think is useful to others, then publish it to the [AzureMonitorCommunity GitHub repo](https://github.com/microsoft/AzureMonitorCommunity). Shoot us an email with a link. We review and publish queries and dashboards to the service so others benefit too. Contact us at [email protected].
112112

113113
## Next steps
114114

articles/active-directory/authentication/concept-fido2-hardware-vendor.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ The following table lists partners who are Microsoft-compatible FIDO2 security k
5353
| Nymi | ![y] | ![n]| ![y]| ![n]| ![n] | https://www.nymi.com/nymi-band |
5454
| Octatco | ![y] | ![y]| ![n]| ![n]| ![n] | https://octatco.com/ |
5555
| OneSpan Inc. | ![n] | ![y]| ![n]| ![y]| ![n] | https://www.onespan.com/products/fido |
56-
| Swissbit | ![n] | ![y]| ![y]| ![n]| ![n] | https://www.swissbit.com/en/products/ishield-fido2/ |
56+
| Swissbit | ![n] | ![y]| ![y]| ![n]| ![n] | https://www.swissbit.com/en/products/ishield-key/ |
5757
| Thales Group | ![n] | ![y]| ![y]| ![n]| ![y] | https://cpl.thalesgroup.com/access-management/authenticators/fido-devices |
5858
| Thetis | ![y] | ![y]| ![y]| ![y]| ![n] | https://thetis.io/collections/fido2 |
5959
| Token2 Switzerland | ![y] | ![y]| ![y]| ![n]| ![n] | https://www.token2.swiss/shop/product/token2-t2f2-alu-fido2-u2f-and-totp-security-key |

articles/active-directory/hybrid/migrate-from-federation-to-cloud-authentication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ Modern authentication clients (Office 2016 and Office 2013, iOS, and Android app
9494
9595
To plan for rollback, use the [documented current federation settings](#document-current-federation-settings) and check the [federation design and deployment documentation](/windows-server/identity/ad-fs/deployment/windows-server-2012-r2-ad-fs-deployment-guide).
9696
97-
The rollback process should include converting managed domains to federated domains by using the [Convert-MSOLDomainToFederated](/powershell/module/microsoft.graph.identity.directorymanagement/new-mgdomainfederationconfiguration?view=graph-powershell-1.0&preserve-view=true) cmdlet. If necessary, configuring extra claims rules.
97+
The rollback process should include converting managed domains to federated domains by using the [New-MgDomainFederationConfiguration](/powershell/module/microsoft.graph.identity.directorymanagement/new-mgdomainfederationconfiguration?view=graph-powershell-1.0&preserve-view=true) cmdlet. If necessary, configuring extra claims rules.
9898
9999
## Migration considerations
100100

articles/active-directory/manage-apps/configure-password-single-sign-on-non-gallery-applications.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-mgmt
99
ms.topic: conceptual
1010
ms.workload: identity
11-
ms.date: 09/22/2021
11+
ms.date: 04/25/2023
1212
ms.author: jomondi
1313
ms.reviewer: alamaral
1414
# Customer intent: As an IT admin, I need to know how to implement password-based single sign-on in Azure Active Directory.
@@ -29,8 +29,8 @@ The configuration page for password-based SSO is simple. It includes only the UR
2929
## Prerequisites
3030

3131
To configure password-based SSO in your Azure AD tenant, you need:
32-
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F)
33-
- One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
32+
- An Azure account with an active subscription. If you don't already have one, you can [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F)
33+
- Global Administrator, or owner of the service principal.
3434
- An application that supports password-based SSO.
3535

3636
## Configure password-based single sign-on

articles/active-directory/standards/index.yml

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ landingContent:
3434
url: configure-azure-active-directory-for-cmmc-compliance.md
3535
- text: Configure Azure Active Directory for HIPAA compliance
3636
url: hipaa-configure-azure-active-directory-for-compliance.md
37+
- text: Configure Azure Active Directory for PCI-DSS compliance
38+
url: azure-ad-pci-dss-guidance.md
3739

3840
# Card
3941
- title: Understand NIST AALs
@@ -113,3 +115,26 @@ landingContent:
113115
- text: Configure other safeguards
114116
url: hipaa-other-controls.md
115117

118+
# Card
119+
- title: Achieve PCI-DSS compliance
120+
linkLists:
121+
- linkListType: how-to-guide
122+
links:
123+
- text: Meet PCI-DSS Requirement 1
124+
url: pci-requirement-1.md
125+
- text: Meet PCI-DSS Requirement 2
126+
url: pci-requirement-2.md
127+
- text: Meet PCI-DSS Requirement 5
128+
url: pci-requirement-5.md
129+
- text: Meet PCI-DSS Requirement 6
130+
url: pci-requirement-6.md
131+
- text: Meet PCI-DSS Requirement 7
132+
url: pci-requirement-7.md
133+
- text: Meet PCI-DSS Requirement 8
134+
url: pci-requirement-8.md
135+
- text: Meet PCI-DSS Requirement 10
136+
url: pci-requirement-10.md
137+
- text: Meet PCI-DSS Requirement 11
138+
url: pci-requirement-11.md
139+
- text: Meet Azure Active Directory PCI-DSS MFA supplemental requirements
140+
url: azure-ad-pci-dss-mfa.md

articles/advisor/advisor-reference-cost-recommendations.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -316,6 +316,18 @@ Apache Spark for Azure Synapse Analytics pool's Autoscale feature automatically
316316

317317
Learn more about [Synapse workspace - EnableSynapseSparkComputeAutoScaleGuidance (Consider enabling autoscale feature on spark compute.)](https://aka.ms/EnableSynapseSparkComputeAutoScaleGuidance).
318318

319+
## Web
320+
321+
### Right-size underutilized App Service plans
322+
323+
We've analyzed the usage patterns of your app service plan over the past 7 days and identified low CPU usage. While certain scenarios can result in low utilization by design, you can often save money by choosing a less expensive SKU while retaining the same features.
324+
325+
> [!NOTE]
326+
> - Currently, this recommendation only works for App Service plans running on Windows on a SKU that allows you to downscale to less expensive tiers without losing any features, like from P3v2 to P2v2 or from P2v2 to P1v2.
327+
> - CPU bursts that last only a few minutes might not be correctly detected. Please perform a careful analysis in your App Service plan metrics blade before downscaling your SKU.
328+
329+
Learn more about [App Service plans](../app-service/overview-hosting-plans.md).
330+
319331
## Azure Monitor
320332

321333
For Azure Monitor cost optimization suggestions, please see [Optimize costs in Azure Monitor](../azure-monitor/best-practices-cost.md).

articles/api-management/mitigate-owasp-api-threats.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The Open Web Application Security Project ([OWASP](https://owasp.org/about/)) Fo
1515
The OWASP [API Security Project](https://owasp.org/www-project-api-security/) focuses on strategies and solutions to understand and mitigate the unique *vulnerabilities and security risks of APIs*. In this article, we'll discuss recommendations to use Azure API Management to mitigate the top 10 API threats identified by OWASP.
1616

1717
> [!NOTE]
18-
> In addition to following the recommendations in this article, you can enable Defender for APIs (preview), a capability of [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction), for API security insights, recommendations, and threat detection. [Learn more about using Defender for APIs with API Management](protect-with-defender-for-apis.md)
18+
> In addition to following the recommendations in this article, you can enable [Defender for APIs](/azure/defender-for-cloud/defender-for-apis-introduction) (preview), a capability of [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction), for API security insights, recommendations, and threat detection. [Learn more about using Defender for APIs with API Management](protect-with-defender-for-apis.md)
1919
2020
## Broken object level authorization
2121

@@ -317,4 +317,4 @@ Learn more about:
317317
* [Security baseline for API Management](/security/benchmark/azure/baselines/api-management-security-baseline)
318318
* [Security controls by Azure policy](security-controls-policy.md)
319319
* [Landing zone accelerator for API Management](/azure/cloud-adoption-framework/scenarios/app-platform/api-management/landing-zone-accelerator)
320-
* [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)
320+
* [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: azcmagent check CLI reference
3+
description: Syntax for the azcmagent check command line tool
4+
ms.topic: reference
5+
ms.date: 04/20/2023
6+
---
7+
8+
# azcmagent check
9+
10+
Run a series of network connectivity checks to see if the agent can successfully communicate with required network endpoints. The command outputs a table showing connectivity test results for each required endpoint, including whether the agent used a private endpoint and/or proxy server.
11+
12+
## Usage
13+
14+
```
15+
azcmagent check [flags]
16+
```
17+
18+
## Examples
19+
20+
Check connectivity with the agent's currently configured cloud and region.
21+
22+
```
23+
azcmagent check
24+
```
25+
26+
Check connectivity with the East US region using public endpoints.
27+
28+
```
29+
azcmagent check --location "eastus"
30+
```
31+
32+
Check connectivity with the Central India region using private endpoints.
33+
34+
```
35+
azcmagent check --location "centralindia" --enable-pls-check
36+
```
37+
38+
## Flags
39+
40+
`--cloud`
41+
42+
Specifies the Azure cloud instance. Must be used with the `--location` flag. If the machine is already connected to Azure Arc, the default value is the cloud to which the agent is already connected. Otherwise, the default value is "AzureCloud".
43+
44+
Supported values:
45+
46+
* AzureCloud (public regions)
47+
* AzureUSGovernment (Azure US Government regions)
48+
* AzureChinaCloud (Azure China regions)
49+
50+
`-l`, `--location`
51+
52+
The Azure region to check connectivity with. If the machine is already connected to Azure Arc, the current region is selected as the default.
53+
54+
Sample value: westeurope
55+
56+
`-p`, `--enable-pls-check`
57+
58+
Checks if supported Azure Arc endpoints resolve to private IP addresses. This flag should be used when you intend to connect the server to Azure using an Azure Arc private link scope.
59+
60+
[!INCLUDE [common-flags](includes/azcmagent-common-flags.md)]

0 commit comments

Comments
 (0)