SOLVED

How to increase the value for MaxConcurrency to O365

%3CLINGO-SUB%20id%3D%22lingo-sub-3017404%22%20slang%3D%22en-US%22%3EHow%20to%20increase%20the%20value%20for%20MaxConcurrency%20to%20O365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3017404%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20product%20faces%20the%20following%20problem%20when%20working%20with%20O365%3A%3C%2FP%3E%3CP%3E%3CEM%3E'Processing%20data%20from%20remote%20server%20outlook.office365.com%20failed%20with%20the%20following%20error%20message%3A%20%5BAuthZRequestId%3Db9bcce6a-4e1f-4128-a630-f68cdfc8a775%5D%5BFailureCategory%3DAuthZ-AuthorizationException%5D%20Fail%20to%20create%20a%20runspace%20because%20you%20have%20exceeded%20the%20maximum%20number%20of%20connections%20allowed%20%3A%203%20for%20the%20policy%20party%20%3A%20MaxConcurrency.%20Please%20close%20existing%20runspace%20and%20try%20again.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20please%20advise%20us%20on%20how%20to%20solve%20this%20problem%3F%3CBR%20%2F%3EOr%20how%20to%20increase%20the%20value%20for%20MaxConcurrency%20to%20O365%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20please%20send%20me%20a%20link%20to%20the%20official%20documentation%20where%20the%20O365%20limits%20are%20described%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20in%20advance%20for%20your%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3017404%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3018870%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20increase%20the%20value%20for%20MaxConcurrency%20to%20O365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3018870%22%20slang%3D%22en-US%22%3EHey%20Stefan%2C%20I%20believe%20I%20already%20answered%20this%20on%20Q%26amp%3BA%2C%20but%20just%20in%20case.%20Those%20values%20are%20pre-configured%20for%20all%20customers%20and%20cannot%20be%20modified.%20Best%20thing%20to%20do%20here%20is%20open%20a%20support%20case%20and%20ask%20for%20exception%2C%20which%20might%20or%20might%20not%20be%20added%20depending%20on%20the%20size%20of%20the%20tenant%2C%20etc.%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20for%20documentation%2C%20Microsoft%20has%20removed%20those%20articles%20a%20long%20time%20ago.%20Afaik%20the%20old%20details%20still%20apply%2C%20which%20in%20this%20particular%20scenario%20should%20be%203%20active%20sessions%20per%20account%2C%2010%20total%20for%20the%20tenant.%3C%2FLINGO-BODY%3E
New Contributor

Hello,

 

Our product faces the following problem when working with O365:

'Processing data from remote server outlook.office365.com failed with the following error message: [AuthZRequestId=b9bcce6a-4e1f-4128-a630-f68cdfc8a775][FailureCategory=AuthZ-AuthorizationException] Fail to create a runspace because you have exceeded the maximum number of connections allowed : 3 for the policy party : MaxConcurrency. Please close existing runspace and try again.

 

Can you please advise us on how to solve this problem?
Or how to increase the value for MaxConcurrency to O365?

 

Can you please send me a link to the official documentation where the O365 limits are described?

 

Thank you in advance for your help.

3 Replies
Hey Stefan, I believe I already answered this on Q&A, but just in case. Those values are pre-configured for all customers and cannot be modified. Best thing to do here is open a support case and ask for exception, which might or might not be added depending on the size of the tenant, etc.

As for documentation, Microsoft has removed those articles a long time ago. Afaik the old details still apply, which in this particular scenario should be 3 active sessions per account, 10 total for the tenant.
best response confirmed by scervenka (New Contributor)
Solution

@scervenka I was wrong, it's actually possible to manage this via the self-service thingy in the M365 Admin center. https://www.michev.info/Blog/Post/3205/self-service-powershell-throttling-policy-relaxation-for-exch...

Thank you very much, Vasil.