operation constraint

Author: OlgaPodo

graph/patterns/longRunningOperations.md

@@ -50,13 +50,14 @@ presentation makes things simpler for our users and tooling chain.
 In general, Microsoft Graph API guidelines for LRO follow [Microsoft REST API
 Guidelines](https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md#13-long-running-operations).
 
-A single deviation from the base guidelines is that Microsoft Graph API standards require that you use the following response headers:
+There are some deviations from the base guidelines where Microsoft Graph API standards require that you do one of the following:
 
-- The Content-Location header indicates the location of a RELO resource.
+- For RELO pattern you should return the Content-Location header that indicates the location of the resource.
   - The API response says the targeted resource is being created by returning a 201 status code and the resource URI is provided in the Content-Location header, but the response indicates that the request is not completed by including "Provisioning" status.
 
-- The Location header indicates the location of a new stepwise operation LRO resource.
+- For LRO pattern you should return the Location header that indicates the location of a new stepwise operation resource.
   - The API response says the operation resource is being created at the URL provided in the Location header and indicates that the request is not completed by including a 202 status code.
+  - Microsoft Graph doesn’t allow tenant wide operation resources therefore stepwise operations is often modeled as a navigation property on the target resource.
 
 ## When to use this pattern