Skip to content

Commit e893b42

Browse files
Merge pull request #314915 from MicrosoftDocs/main
Auto Publish – main to live - 2026-04-20 06:00 UTC
2 parents a4b1e0b + 791b53f commit e893b42

3 files changed

Lines changed: 2 additions & 22 deletions

File tree

articles/active-directory-b2c/implicit-flow-single-page-application.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -267,4 +267,4 @@ GET https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/{policy}/oauth2/v2.0/
267267

268268
## Next steps
269269

270-
See the code sample: [Sign-in with Azure AD B2C in a JavaScript SPA](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-browser-samples/VanillaJSTestApp2.0/app/b2c).
270+
See the code sample: [Sign-in with Azure AD B2C in a JavaScript SPA](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples).

articles/azure-netapp-files/create-active-directory-connections.md

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -302,26 +302,6 @@ Once configured, the AD connection of the NetApp account is used when you create
302302
>[!IMPORTANT]
303303
>The scope of each AD configuration is limited to its parent NetApp account.
304304
305-
### Register the feature
306-
307-
The ability to create one AD connection per NetApp account is generally available. You need to register the feature before using it for the first time. After registration, the feature is enabled and works in the background.
308-
309-
1. Register the feature:
310-
```azurepowershell-interactive
311-
Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFMultipleActiveDirectory
312-
```
313-
314-
2. Check the status of the feature registration:
315-
316-
> [!NOTE]
317-
> The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to`Registered`. Wait until the status is **Registered** before continuing.
318-
319-
```azurepowershell-interactive
320-
Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFMultipleActiveDirectory
321-
```
322-
323-
You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status.
324-
325305
## <a name="shared_ad"></a>Map multiple NetApp accounts in the same subscription and region to one AD connection (preview)
326306
327307
The Shared AD feature enables all NetApp accounts to share an AD connection created by one of the NetApp accounts that belong to the same subscription and the same region. For example, using this feature, all NetApp accounts in the same subscription and region can use the common AD configuration to create an [SMB volume](azure-netapp-files-create-volumes-smb.md), a [NFSv4.1 Kerberos volume](configure-kerberos-encryption.md), or a [dual-protocol volume](create-volumes-dual-protocol.md). When you use this feature, the AD connection is visible in all NetApp accounts that are under the same subscription and same region.

articles/backup/azure-file-share-support-matrix.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ Migration of file shares protected with snapshot backup to vaulted backup is sup
122122
| Setting | Limit |
123123
| --------------------------------------- | ------ |
124124
| Maximum size of file share | 10 TB |
125-
| Maximum number of files in a file share | 10 million |
125+
| Maximum number of files and folders in a file share | 10 million |
126126

127127
>[!Note]
128128
>If you have multiple backups scheduled per day, only the last scheduled snapshot of the day is transferred to the vault.

0 commit comments

Comments
 (0)