Skip to content

Commit 67fd21a

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into storage-network-security
2 parents 390a052 + 3f0b2a4 commit 67fd21a

File tree

222 files changed

+3373
-2102
lines changed

Some content is hidden

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

222 files changed

+3373
-2102
lines changed

.openpublishing.publish.config.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -994,6 +994,7 @@
994994
".openpublishing.redirection.app-service.json",
995995
".openpublishing.redirection.azure-arc-data.json",
996996
".openpublishing.redirection.azure-attestation.json",
997+
".openpublishing.redirection.azure-app-configuration.json",
997998
".openpublishing.redirection.azure-australia.json",
998999
".openpublishing.redirection.azure-databricks.json",
9991000
".openpublishing.redirection.azure-hpc.json",
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
{
2+
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/azure-app-configuration/howto-backup-config-store.md",
5+
"redirect_url": "/articles/azure-app-configuration/concept-geo-replication.md",
6+
"redirect_document_id": false
7+
}
8+
]
9+
}

.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

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22562,6 +22562,11 @@
2256222562
"source_path_from_root": "/articles/azure-monitor/app/java-standalone-arguments.md",
2256322563
"redirect_url": "/azure/azure-monitor/app/java-get-started-supplemental",
2256422564
"redirect_document_id": true
22565+
},
22566+
{
22567+
"source_path_from_root": "/articles/healthcare-apis/dicom/dicom-cast-access-request.md",
22568+
"redirect_url": "/azure/healthcare-apis/dicom/dicom-cast-overview",
22569+
"redirect_document_id": false
2256522570
}
2256622571
]
2256722572
}

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/external-identities/authentication-conditional-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ When an Azure AD organization shares resources with external users with an ident
4646

4747
The following diagram illustrates the authentication flow when an external user signs in with an account from a non-Azure AD identity provider, such as Google, Facebook, or a federated SAML/WS-Fed identity provider.
4848

49-
[ ![Diagram showing the Authentication flow for B2B guest users from an external directory.](media/authentication-conditional-access/authentication-flow-b2b-guests.png) ](media/authentication-conditional-access/authentication-flow-b2b-guests.png#lightbox))
49+
[ ![Diagram showing the Authentication flow for B2B guest users from an external directory.](media/authentication-conditional-access/authentication-flow-b2b-guests.png) ](media/authentication-conditional-access/authentication-flow-b2b-guests.png#lightbox)
5050

5151
| Step | Description |
5252
|--------------|-----------------------|

articles/active-directory/fundamentals/secure-external-access-resources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Both methods have drawbacks. For more information, see the following table.
3939
| Area of concern | Local credentials | Federation |
4040
|----|---|---|
4141
| Security | - Access continues after external user terminates<br> - UserType is Member by default, which grants too much default access | - No user-level visibility <br> - Unknown partner security posture|
42-
| Expense | - Password and multi-factor authentication (MFA) management<br> - Onboarding process<br> - Identity cleanup<br> - Overhead of running a separate directory | Small partners can't afford the infrastructure, lack expertise, and might user consumer email|
42+
| Expense | - Password and multi-factor authentication (MFA) management<br> - Onboarding process<br> - Identity cleanup<br> - Overhead of running a separate directory | Small partners can't afford the infrastructure, lack expertise, and might use consumer email|
4343
| Complexity | Partner users manage more credentials | Complexity grows with each new partner, and increased for partners|
4444

4545
Azure Active Directory (Azure AD) B2B integrates with other tools in Azure AD, and Microsoft 365 services. Azure AD B2B simplifies collaboration, reduces expense, and increases security.

0 commit comments

Comments
 (0)