A number of partners and customers have requirements around blocking or restricting access to trusted IP addresses and ranges in order to secure their data and meet various internal requirements and industry certifications.
rhipe does not in any way support the removal of Partner Permissions on tenancies. This is required to maintain partner discounting, especially in regards to Azure Consumption. The removal of partner permissions on a tenant may result in you being charged Azure Consumption at retail rate plus an invoicing fee.
The correct way of controlling access to tenants is via Conditional Access Policies in Azure AD. This allows you to block access from unknown places and networks, and is a requirement to meet various security certifications. Microsoft services like Azure are compliant with most security certifications (PCI DSS, SOX, HIPAA, ISO) however only when the resources in Azure are configured correctly. Conditional Access is one of the requirements to meet these security compliance programs.
Conditional Access allows you to his means you can restrict access to your tenancy as a whole, or by discrete services. Unfortunately by doing this, it can affect our technical support team to assist you define, isolate, replicate and resolve your issues. We are also often unable to raise an escalation request as we require access via Delegated Permissions to your Office 365 Admin Portal or other Microsoft administration portals to raise these cases.
Where partners have restricted access globally, we ask that you create a 'rhipe' conditional access Location Policy, and add the following IP's to it. When you need to grant us access, simply mark that range as trusted until we have been able to resolve your issue, then remove the trusted flag once the issue is resolved.
Our support teams IP addresses are:
Please note that this list is subject to change and you should check this KB article (and last revised date) to ensure your conditional access group matches the above.
Conditional Access network locations require CIDR notation within AzureAD. For a single IPv4 address, add '/32' to the end of the IP which signifies a single IP range. IPv6 addressing can vary in local networks, but a single IPv6 address will require a '/128' as a suffix.
Last update: 20/2/2020
rhipe CSP Support Guide
Introduction As a rhipe Limited (ACN 112 452 436) customer, it is our pleasure to welcome you to our Global CSP Support Services. With operations around the globe, we are backed by a team of highly trained and experienced technical support engineers ...
Octopus Cloud - Cloud View Support Terms
Octopus Cloud - Cloud View Support Terms V2 0 09 10 2020 - Version October 2020 Octopus Cloud has developed its Cloud View product (as further defined below), which currently consists of a report generator solution, which can be subscribed to for a ...
Logging support tickets on behalf of Partners
Revisions Revised by Dan Martin Nature of Update Confirmed this is still active process Date of Revision 8/12/2021' Revisions Revised by Dan Martin Nature of Update Confirmed this is still active process Date of Revision 8/12/2021 Logging support ...
Prime API Access
Revisions Revised by Bryan Donsal Nature of Update Template is still relevant Date of Revision 10/25/22 Category Prism Portal CSP Dear xxxx, Thank you for your interest in rhipe’s Prime Portal APIs. These APIs have been built from ground up to ...
rhipe Granular Delegated Admin Permissions (GDAP) Policy and Process
rhipe is committed to the new Granular Delegated Admin Permissions (GDAP) for partners being rolled out by Microsoft. Unfortunately, the implementation by Microsoft requires that each relationship is commenced from a unique and time-limited URL, and ...