Skype Operations Framework

We want to hear from you about how you are using the tools and assets, what works and what does not.
If you feel there is anything missing, or have any other feedback that you would like to provide to our team.

When submitting a new idea:

For feedback items, please select the phase most relevant to your feedback: Plan, Deliver or Operate.

For any corrections that need to be made to any of the assets, please select Content Corrections and include the asset title and page/slide number.

For any feedback on trainings, please select Training

We believe that this site is the best place to provide your feedback.
If you want to contact the SOF team for non-feedback items then please use the following email address SOF@microsoft.com.

How can we improve SOF?

Enter your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

Usage of "CIDR" on slides 12 and 13 is incorrect. CIDR refers to allowing a variable length subnet mask, where as classful address assumed the mask based on the IP subnet. For example, 10.1.2.3 was assumed to have a /8 subnet mask. CIDR allows 10.1.2.3/24, for example, to be used instead.

CIDR is not supernetting.

The example on slide 12 for supernetting is otherwise correct - supernetting is using a subnet with a smaller mask to represent some or all of the smaller possible subnets within the range of IPs represented by the supernet. A subnet is defined on a routing interface, a supernet is not.

Usage of "CIDR" on slides 12 and 13 is incorrect. CIDR refers to allowing a variable length subnet mask, where as classful address assumed the mask based on the IP subnet. For example, 10.1.2.3 was assumed to have a /8 subnet mask. CIDR allows 10.1.2.3/24, for example, to be used instead.

CIDR is not supernetting.

The example on slide 12 for supernetting is otherwise correct - supernetting is using a subnet with a smaller mask to represent some or all of the smaller possible subnets within the range of IPs represented by the supernet. A subnet is defined on a…

In the "6- Design-Cloud PBX Architecture, Coexistence, and Migration Design Document-v2.4.docx", it states that a toll-free number "can handle up to 100 simultaneous calls". This seems like a big limitation for a toll-free dial-in number being shared in an enterprise, and this information is not found on any of the Office support sites. Is this an accurate statement on the limitation?

If any files are updated, please update the timestamp for Last Updated on the top of the page so that people know there actually was an update. Additionally, for files labeled v1 that are updated, please update the version to again show us there was an update.
My experience specifically was with the bulk user enable script, but I suspect other pages might have updates that nobody knows about simply because there's no visual indication on the website.

I believe there is an incorrect statement on Page 5 of the Usage.docx file that is included in the Network Assessment Tool.

The document currently reads "In this sample, the 70.5 ms RTT latency meets the target for a test performed from a customer’s network edge site but does not meet the target for a test performed on a client machine."

However, the image shows the RTT Latency passed from the Client machine to the Microsoft Network Edge, and Failed from a network Edge connecting the the Microsoft network Edge.

So I would think the statement should be reversed, "In this sample, the 70.5 ms RTT latency meets the target for a test performed from a client machine but does not meet the target for a test performed from a customer’s network edge site."

I believe there is an incorrect statement on Page 5 of the Usage.docx file that is included in the Network Assessment Tool.

The document currently reads "In this sample, the 70.5 ms RTT latency meets the target for a test performed from a customer’s network edge site but does not meet the target for a test performed on a client machine."

However, the image shows the RTT Latency passed from the Client machine to the Microsoft Network Edge, and Failed from a network Edge connecting the the Microsoft network Edge.