ASP.NET ActiveDirectoryMembershipProvider and port 445 (SMB)
While AD Membership is no longer recommended for use (use ADFS or something more modern instead), and is no longer being actively developed, we still see it from time-to-time here in support. One issue when using System.Web.Security.ActiveDirectoryMembershipProvider I've personally seen a couple times is the provider failing when port 445 is either inaccessible or blocked. When setting-up this provider with Active Directory, port 445 between the app server and Domain Controllers must be open and usable.Biz Apps Net Customer Add: How to drive numbers for CSP and EA?
We want to understand how we as a partner can drive the net customer add numbers in the partner portal. We believe that we need to establish a DPOR for EA customers, is that correct? Scenario A - We have acquired a new customer, we provide their licences, type is CSP. Scenario B - We have acquired a new customer, we provide their licences, type is EA Impact on the Net Customer Add figure: Scenario A: No "additional" action is required. Once the agreement is current and active, the new customer will be included in the next data refresh of the partner portal. Note: May take up to 30 days before data is propagated to the partner portal. Scenario B: "Additional" action is required": If the license agreement is EA, and we don't undertake any additional steps, we will NOT see the customer be added to our net customer add figure. To correct this and get recognition for this new customer we need to establish a DPOR relationship in the customers Azure environment, as described in the KC (https://learn.microsoft.com/en-us/partner-center/link-partner-id-for-azure-performance-pal-dpor) Is our understanding correct? What's missing or what's worth to keep in mind too? Thank you! Ralf
