Skip to content

Commit 16831d0

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents f3e5ffb + cfd5d50 commit 16831d0

File tree

619 files changed

+3369
-4066
lines changed

Some content is hidden

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

619 files changed

+3369
-4066
lines changed

.openpublishing.redirection.json

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,20 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/visual-studio/vs-storage-cloud-services-getting-started-blobs.md",
5+
"redirect_url": "/previous-versions/azure/visual-studio/vs-storage-cloud-services-getting-started-blobs",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/visual-studio/vs-storage-cloud-services-getting-started-queues.md",
10+
"redirect_url": "/previous-versions/azure/visual-studio/vs-storage-cloud-services-getting-started-queues",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/visual-studio/vs-storage-cloud-services-getting-started-tables.md",
15+
"redirect_url": "/previous-versions/azure/visual-studio/vs-storage-cloud-services-getting-started-tables",
16+
"redirect_document_id": false
17+
},
318
{
419
"source_path": "articles/automanage/automanage-virtual-machines.md",
520
"redirect_url": "/azure/automanage/index",
@@ -29363,6 +29378,31 @@
2936329378
"source_path": "articles/aks/howto-deploy-java-liberty-app-with-postgresql.md",
2936429379
"redirect_url": "/azure/developer/java/ee/howto-deploy-java-liberty-app-manual",
2936529380
"redirect_document_id": false
29381+
},
29382+
{
29383+
"source_path": "articles/virtual-machines/workloads/redhat/jboss-eap-on-rhel.md",
29384+
"redirect_url": "/azure/developer/java/ee/jboss-on-azure",
29385+
"redirect_document_id": false
29386+
},
29387+
{
29388+
"source_path": "articles/virtual-machines/workloads/redhat/jboss-eap-marketplace-image.md",
29389+
"redirect_url": "/azure/developer/java/ee/jboss-on-azure",
29390+
"redirect_document_id": false
29391+
},
29392+
{
29393+
"source_path": "articles/virtual-machines/workloads/redhat/jboss-eap-on-azure-best-practices.md",
29394+
"redirect_url": "/azure/developer/java/ee/jboss-on-azure",
29395+
"redirect_document_id": false
29396+
},
29397+
{
29398+
"source_path": "articles/virtual-machines/workloads/redhat/jboss-eap-on-azure-migration.md",
29399+
"redirect_url": "/azure/developer/java/ee/jboss-on-azure",
29400+
"redirect_document_id": false
29401+
},
29402+
{
29403+
"source_path": "articles/virtual-machines/workloads/redhat/wildfly-on-centos.md",
29404+
"redirect_url": "/azure/developer/java/ee/jboss-on-azure",
29405+
"redirect_document_id": false
2936629406
}
2936729407
]
2936829408
}

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

Lines changed: 37 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -15,47 +15,61 @@ ms.collection: M365-identity-device-management
1515

1616
Most hacking related breaches use either stolen or weak passwords. Often, IT will enforce stronger password complexity or frequent password changes to reduce the risk of a security incident. However, this increases help desk costs and leads to poor user experiences as users are required to memorize or store new, complex passwords.
1717

18-
FIDO2 security keys offer an alternative. FIDO2 security keys can replace weak credentials with strong hardware-backed public/private-key credentials which cannot be reused, replayed, or shared across services. Security keys support shared device scenarios, allowing you to carry your credential with you and safely authenticate to an Azure Active Directory joined Windows 10 device that’s part of your organization.
18+
FIDO2 security keys offer an alternative. FIDO2 security keys can replace weak credentials with strong hardware-backed public/private-key credentials which can't be reused, replayed, or shared across services. Security keys support shared device scenarios, allowing you to carry your credential with you and safely authenticate to an Azure Active Directory joined Windows 10 device that’s part of your organization.
1919

2020
Microsoft partners with FIDO2 security key vendors to ensure that security devices work on Windows, the Microsoft Edge browser, and online Microsoft accounts, to enable strong password-less authentication.
2121

2222
You can become a Microsoft-compatible FIDO2 security key vendor through the following process. Microsoft doesn't commit to do go-to-market activities with the partner and will evaluate partner priority based on customer demand.
2323

24-
1. First, your authenticator needs to have a FIDO2 certification. We will not be able to work with providers who do not have a FIDO2 certification. To learn more about the certification, please visit this website: [https://fidoalliance.org/certification/](https://fidoalliance.org/certification/)
24+
1. First, your authenticator needs to have a FIDO2 certification. We won't be able to work with providers who don't have a FIDO2 certification. To learn more about the certification, please visit this website: [https://fidoalliance.org/certification/](https://fidoalliance.org/certification/)
2525
2. After you have a FIDO2 certification, please fill in your request to our form here: [https://forms.office.com/r/NfmQpuS9hF](https://forms.office.com/r/NfmQpuS9hF). Our engineering team will only test compatibility of your FIDO2 devices. We won't test security of your solutions.
2626
3. Once we confirm a move forward to the testing phase, the process usually take about 3-6 months. The steps usually involve:
2727
- Initial discussion between Microsoft and your team.
2828
- Verify FIDO Alliance Certification or the path to certification if not complete
2929
- Receive an overview of the device from the vendor
3030
- Microsoft will share our test scripts with you. Our engineering team will be able to answer questions if you have any specific needs.
31-
- You will complete and send all passed results to Microsoft Engineering team
31+
- You'll complete and send all passed results to Microsoft Engineering team
3232
4. Upon successful passing of all tests by Microsoft Engineering team, Microsoft will confirm vendor's device is listed in [the FIDO MDS](https://fidoalliance.org/metadata/).
3333
5. Microsoft will add your FIDO2 Security Key on Azure AD backend and to our list of approved FIDO2 vendors.
3434

3535
## Current partners
3636

3737
The following table lists partners who are Microsoft-compatible FIDO2 security key vendors.
3838

39-
| **Provider** | **Link** |
40-
| --- | --- |
41-
| AuthenTrend | [https://authentrend.com/about-us/#pg-35-3](https://authentrend.com/about-us/#pg-35-3) |
42-
| Ensurity | [https://www.ensurity.com/contact](https://www.ensurity.com/contact) |
43-
| Excelsecu | [https://www.excelsecu.com/productdetail/esecufido2secu.html](https://www.excelsecu.com/productdetail/esecufido2secu.html) |
44-
| Feitian | [https://ftsafe.us/pages/microsoft](https://ftsafe.us/pages/microsoft) |
45-
| Go-Trust ID | [https://www.gotrustid.com/](https://www.gotrustid.com/idem-key) |
46-
| HID | [https://www.hidglobal.com/contact-us](https://www.hidglobal.com/contact-us) |
47-
| Hypersecu | [https://www.hypersecu.com/hyperfido](https://www.hypersecu.com/hyperfido) |
48-
| IDmelon Technologies Inc. | [https://www.idmelon.com/#idmelon](https://www.idmelon.com/#idmelon) |
49-
| Kensington | [https://www.kensington.com/solutions/product-category/why-biometrics/](https://www.kensington.com/solutions/product-category/why-biometrics/) |
50-
| KONA I | [https://konai.com/business/security/fido](https://konai.com/business/security/fido) |
51-
| Nymi | [https://www.nymi.com/product](https://www.nymi.com/product) |
52-
| OneSpan Inc. | [https://www.onespan.com/products/fido](https://www.onespan.com/products/fido) |
53-
| Thales | [https://cpl.thalesgroup.com/access-management/authenticators/fido-devices](https://cpl.thalesgroup.com/access-management/authenticators/fido-devices) |
54-
| Thetis | [https://thetis.io/collections/fido2](https://thetis.io/collections/fido2) |
55-
| Token2 Switzerland | [https://www.token2.swiss/shop/product/token2-t2f2-alu-fido2-u2f-and-totp-security-key](https://www.token2.swiss/shop/product/token2-t2f2-alu-fido2-u2f-and-totp-security-key) |
56-
| TrustKey Solutions | [https://www.trustkeysolutions.com/security-keys/](https://www.trustkeysolutions.com/security-keys/) |
57-
| VinCSS | [https://passwordless.vincss.net](https://passwordless.vincss.net/) |
58-
| Yubico | [https://www.yubico.com/solutions/passwordless/](https://www.yubico.com/solutions/passwordless/) |
39+
| Provider | Biometric | USB | NFC | BLE | FIPS Certified | Contact |
40+
|---------------------------|:-----------------:|:---:|:---:|:---:|:--------------:|-----------------------------------------------------------------------------------------------------|
41+
| AuthenTrend | ![y] | ![y]| ![y]| ![y]| ![n] | https://authentrend.com/about-us/#pg-35-3 |
42+
| Ciright | ![n] | ![n]| ![y]| ![n]| ![n] | https://www.cyberonecard.com/ |
43+
| Crayonic | ![y] | ![n]| ![y]| ![y]| ![n] | https://www.crayonic.com/keyvault |
44+
| Ensurity | ![y] | ![y]| ![n]| ![n]| ![n] | https://www.ensurity.com/contact |
45+
| Excelsecu | ![y] | ![y]| ![y]| ![y]| ![n] | https://www.excelsecu.com/productdetail/esecufido2secu.html |
46+
| Feitian | ![y] | ![y]| ![y]| ![y]| ![y] | https://shop.ftsafe.us/pages/microsoft |
47+
| Fortinet | ![n] | ![y]| ![n]| ![n]| ![n] | https://www.fortinet.com/ |
48+
| Giesecke + Devrient (G+D) | ![y] | ![y]| ![y]| ![y]| ![n] | https://www.gi-de.com/en/identities/enterprise-security/hardware-based-authentication |
49+
| GoTrustID Inc. | ![n] | ![y]| ![y]| ![y]| ![n] | https://www.gotrustid.com/idem-key |
50+
| HID | ![n] | ![y]| ![y]| ![n]| ![n] | https://www.hidglobal.com/contact-us |
51+
| Hypersecu | ![n] | ![y]| ![n]| ![n]| ![n] | https://www.hypersecu.com/hyperfido |
52+
| IDmelon Technologies Inc. | ![y] | ![y]| ![y]| ![y]| ![n] | https://www.idmelon.com/#idmelon |
53+
| Kensington | ![y] | ![y]| ![n]| ![n]| ![n] | https://www.kensington.com/solutions/product-category/why-biometrics/ |
54+
| KONA I | ![y] | ![n]| ![y]| ![y]| ![n] | https://konai.com/business/security/fido |
55+
| NeoWave | ![n] | ![y]| ![y]| ![n]| ![n] | https://neowave.fr/en/products/fido-range/ |
56+
| Nymi | ![y] | ![n]| ![y]| ![n]| ![n] | https://www.nymi.com/nymi-band |
57+
| Octatco | ![y] | ![y]| ![n]| ![n]| ![n] | https://octatco.com/ |
58+
| OneSpan Inc. | ![n] | ![y]| ![n]| ![y]| ![n] | https://www.onespan.com/products/fido |
59+
| Swissbit | ![n] | ![y]| ![y]| ![n]| ![n] | https://www.swissbit.com/en/products/ishield-fido2/ |
60+
| Thales Group | ![n] | ![y]| ![y]| ![n]| ![y] | https://cpl.thalesgroup.com/access-management/authenticators/fido-devices |
61+
| Thetis | ![y] | ![y]| ![y]| ![y]| ![n] | https://thetis.io/collections/fido2 |
62+
| Token2 Switzerland | ![y] | ![y]| ![y]| ![n]| ![n] | https://www.token2.swiss/shop/product/token2-t2f2-alu-fido2-u2f-and-totp-security-key |
63+
| TrustKey Solutions | ![y] | ![y]| ![n]| ![n]| ![n] | https://www.trustkeysolutions.com/security-keys/ |
64+
| VinCSS | ![n] | ![y]| ![n]| ![n]| ![n] | https://passwordless.vincss.net |
65+
| Yubico | ![y] | ![y]| ![y]| ![n]| ![y] | https://www.yubico.com/solutions/passwordless/ |
66+
67+
68+
69+
<!--Image references-->
70+
[y]: ./media/fido2-compatibility/yes.png
71+
[n]: ./media/fido2-compatibility/no.png
72+
5973

6074
## Next steps
6175

articles/active-directory/external-identities/add-user-without-invite.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,6 @@ ms.date: 08/05/2020
1313
ms.author: mimart
1414
author: msmimart
1515
manager: celestedg
16-
ms.reviewer: elisol
1716

1817
ms.collection: M365-identity-device-management
1918
---

articles/active-directory/external-identities/add-users-administrator.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@ ms.date: 08/31/2022
1212
ms.author: mimart
1313
author: msmimart
1414
manager: celestedg
15-
1615
ms.collection: M365-identity-device-management
1716
---
1817

articles/active-directory/external-identities/add-users-information-worker.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@ ms.date: 12/19/2018
1212
ms.author: mimart
1313
author: msmimart
1414
manager: celestedg
15-
ms.reviewer: mal
1615
ms.custom: "it-pro, seo-update-azuread-jan"
1716
ms.collection: M365-identity-device-management
1817
---

articles/active-directory/external-identities/api-connectors-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
1717
# Use API connectors to customize and extend self-service sign-up
1818

1919
## Overview
20-
As a developer or IT administrator, you can use API connectors to integrate your [self-service sign-up user flows](self-service-sign-up-overview.md) with web APIs to customize the sign-up experience and integrate with external systems. For example, with API connectors, you can:
20+
As a developer or IT administrator, you can use [API connectors](self-service-sign-up-add-api-connector.md#create-an-api-connector) to integrate your [self-service sign-up user flows](self-service-sign-up-overview.md) with web APIs to customize the sign-up experience and integrate with external systems. For example, with API connectors, you can:
2121

2222
- [**Integrate with a custom approval workflow**](self-service-sign-up-add-approvals.md). Connect to a custom approval system for managing and limiting account creation.
2323
- [**Perform identity verification**](code-samples-self-service-sign-up.md#identity-verification). Use an identity verification service to add an extra level of security to account creation decisions.
@@ -55,4 +55,4 @@ An API connector at this step in the sign-up process is invoked after the attrib
5555

5656
## Next steps
5757
- Learn how to [add an API connector to a user flow](self-service-sign-up-add-api-connector.md)
58-
- Learn how to [add a custom approval system to self-service sign-up](self-service-sign-up-add-approvals.md)
58+
- Learn how to [add a custom approval system to self-service sign-up](self-service-sign-up-add-approvals.md)

articles/active-directory/external-identities/auditing-and-reporting.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,6 @@ ms.date: 05/11/2020
1111
ms.author: mimart
1212
author: msmimart
1313
manager: celestedg
14-
ms.reviewer: mal
1514
ms.custom: "it-pro, seo-update-azuread-jan"
1615
ms.collection: M365-identity-device-management
1716
---

articles/active-directory/external-identities/b2b-tutorial-require-mfa.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,6 @@ ms.date: 01/07/2022
1111
ms.author: mimart
1212
author: msmimart
1313
manager: CelesteDG
14-
ms.reviewer: mal
1514
ms.custom: "it-pro, seo-update-azuread-jan"
1615
ms.collection: M365-identity-device-management
1716
---

articles/active-directory/external-identities/bulk-invite-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.date: 02/11/2020
1212
ms.author: mimart
1313
author: msmimart
1414
manager: celestedg
15-
ms.reviewer: mal
15+
1616

1717
# Customer intent: As a tenant administrator, I want to send B2B invitations to multiple external users at the same time so that I can avoid having to send individual invitations to each user.
1818

articles/active-directory/external-identities/claims-mapping.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.date: 04/06/2018
1111
ms.author: mimart
1212
author: msmimart
1313
manager: celestedg
14-
ms.reviewer: elisolMS
14+
1515

1616
ms.collection: M365-identity-device-management
1717
---

0 commit comments

Comments
 (0)