Skip to content

Commit 2ad95e7

Browse files
Merge pull request #241718 from jaep3347/patch-8
Update project-share-custom-models.md
2 parents 163e394 + 7d68b81 commit 2ad95e7

File tree

1 file changed

+2
-25
lines changed

1 file changed

+2
-25
lines changed

articles/applied-ai-services/form-recognizer/how-to-guides/project-share-custom-models.md

Lines changed: 2 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -20,42 +20,19 @@ Form Recognizer Studio is an online tool to visually explore, understand, train,
2020

2121
In order to share and import your custom extraction projects seamlessly, both users (user who shares and user who imports) need an An active [**Azure account**](https://azure.microsoft.com/free/cognitive-services/). If you don't have one, you can [**create a free account**](https://azure.microsoft.com/free/). Also, both users need to configure permissions to grant access to the Form Recognizer and storage resources.
2222

23+
Generally, in the process of creating a custom model project, most of the requirements should have been met for project sharing. However, in cases where the project sharing feature does not work, please check the below.
24+
2325
## Granted access and permissions
2426

2527
> [!IMPORTANT]
2628
> Custom model projects can be imported only if you have the access to the storage account that is associated with the project you are trying to import. Check your storage account permission before starting to share or import projects with others.
2729
28-
### Managed identity
29-
30-
Enable a system-assigned managed identity for your Form Recognizer resource. A system-assigned managed identity is enabled directly on a service instance. It isn't enabled by default; you must go to your resource and update the identity setting.
31-
32-
For more information, *see*, [Enable a system-assigned managed identity](../managed-identities.md#enable-a-system-assigned-managed-identity)
33-
34-
### Role-based access control (RBAC)
35-
36-
Grant your Form Recognizer managed identity access to your storage account using Azure role-based access control (Azure RBAC). The [Storage Blob Data Contributor](../../..//role-based-access-control/built-in-roles.md#storage-blob-data-reader) role grants read, write, and delete permissions for Azure Storage containers and blobs.
37-
38-
For more information, *see*, [Grant access to your storage account](../managed-identities.md#grant-access-to-your-storage-account)
39-
40-
### Configure cross origin resource sharing (CORS)
41-
42-
CORS needs to be configured in your Azure storage account for it to be accessible to the Form Recognizer Studio. You can update the CORS setting in the Azure portal.
43-
44-
Form more information, *see* [Configure CORS](../quickstarts/try-form-recognizer-studio.md#configure-cors)
45-
4630
### Virtual networks and firewalls
4731

4832
If your storage account VNet is enabled or if there are any firewall constraints, the project can't be shared. If you want to bypass those restrictions, ensure that those settings are turned off.
4933

5034
A workaround is to manually create a project using the same settings as the project being shared.
5135

52-
### User sharing requirements
53-
54-
Users sharing the project need to create a project [**`ListAccountSAS`**](/rest/api/storagerp/storage-accounts/list-account-sas) to configure the storage account CORS and a [**`ListServiceSAS`**](/rest/api/storagerp/storage-accounts/list-service-sas) to generate a SAS token for *read*, *write* and *list* container's file in addition to blob storage data *update* permissions.
55-
56-
### User importing requirements
57-
58-
Users who want to import the project need a [**`ListServiceSAS`**](/rest/api/storagerp/storage-accounts/list-service-sas) to generate a SAS token for *read*, *write* and *list* container's file in addition to blob storage data *update* permissions.
5936

6037
## Share a custom extraction model with Form Recognizer studio
6138

0 commit comments

Comments
 (0)