Add timeframe for CT registration #10348
Conversation
cindylay
changed the title
|
Learn Build status updates of commit 97138cb:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/embedded/getting-started/register-api-documentation.md | View | Details |
docs/embedded/getting-started/register-api-documentation.md
- Line 16, Column 1: [Warning: invalid-note-section]
Text in the first line of Note/Section/Video is not valid. Will be rendered to <blockquote>
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
|
||
| Since the registration API controls the permissions that a SharePoint Embedded application can perform against the container in the consuming tenant, this call should be one of the first APIs invoked. Failure to do so results in access denied errors when invoking other APIs against the container and/or the content in the containers. | ||
|
|
||
| There are no restrictions on how many times the registration API can be invoked. How often the registration API is invoked and when it's invoked is dependent on the SharePoint Embedded application. However, the last successful call to the registration API determines the settings used in the consuming tenant. | ||
|
|
||
| > [!NOTE] : Container type registration may fail if attempted immediately after tenant creation. To avoid issues, wait at least two hours after tenant creation before registering a container type. |
There was a problem hiding this comment.
This is formatted incorrectly, the < [!NOTE] should be followed by nothing else. Content should be on the next line:
> [!NOTE]
> Container type ....Currently, it renders like this (see preview URL):
There was a problem hiding this comment.
Also, this is going into the new Registration API doc (Graph docs):
The registration of a container type in a newly created tenant can fail if the tenant isn't yet fully ready. You might need to wait at least an hour before you can register a container type in a new tenant.
One says up to one hour, and the other says up to two hours.
Should get in sync on this @javieralvarezchiang
There was a problem hiding this comment.
I think we should instead remove the delay (we have a plan that might work) I'm not too concerned about the inconsistencies. In my tests I added a 5 min delay between CT and CT registration, and that was enough. But I can't guarantee that it is always the case (I know it is for the new APIs)
There was a problem hiding this comment.
We should document what the customer promise is. If there’s a difference in behaviour between the new API and the current registration API, then we should first document the current behaviour in this PR.
When the new APIs go out, we would need to change this whole article to point to the new APIs anyway and would update the customer promise then. @javieralvarezchiang
Category