Aclarando las nubes
•Descargar como PPTX, PDF•
0 recomendaciones•438 vistas
El documento proporciona información sobre Office 365 y Windows Azure, incluyendo cuándo usar cada uno, los modelos de licenciamiento de Office 365, los beneficios para partners, y las opciones para agregar aplicaciones y características de publicación. También presenta a Mario Cortés como el líder de SharePoint de Plain Concepts y proporciona su contacto de correo electrónico.
Recomendados
Más contenido relacionado
Destacado
Destacado (9)
Similar a Aclarando las nubes
Similar a Aclarando las nubes (20)
Más de Mario Cortés Flores
Más de Mario Cortés Flores (20)
Último
Último (20)
Aclarando las nubes
- 12. 99.95%
- 16. Windows Azure
- 18. Qué es Office 365 W15 La familia de Office 365 W15:
- 19. OnlineOn Premises Hybrid Cloud según tus necesidades Messaging Voice & Video Content Management Enterprise Social Reporting & Analytics La major experiencia entre dispositivos Integrando mejores soluciones
- 20. Modelo de licenciamiento Basado en suscripciones Pensado para distintos modelos Home, Small business y Enterprise
- 22. Beneficios para Partners Vender licencias Beneficios
- 25. Barra superior disponible en todos los servicios Panel informative a modo de resumen Informes, usuarios, do minios, configuración de servicios,…
- 26. Powershell PowerShell para Office365 SharePoint Online
- 31. Log in to Office 365 from a browser to update your user profile and install the latest version of the Office apps Select your language to start installing the new Office apps El Nuevo Offic se descaga mediante streaming en tu PC
- 32. Nueva opción para actualizar por colección Nueva sección para las aplicaciones
- 34. Apps Nuevo modelo Tipos de Apps Opciones de Hosting
- 35. Office 365
- 36. Windows Azure y Office365 Apps y Workflows Identidad
- 37. Overview Windows Azure Windows Azure Training Kit - December 2012 Windows Azure, Java y Eclipse Trial Windows Azure
- 38. Mario Cortés Flores SharePoint Lead Plain Concepts mcortes@plainconcepts.com
Notas del editor
- Slide Objectives:Explain how Microsoft thinks of the cloudSpeaker Notes:There are numerous terms and definitions floating around in the industry for “the cloud”, “cloud computing”, “cloud services”, etc.Microsoft thinks of the cloud as simply an approach to computing that enables applications to be delivered at scale for a variety of workloads and client devices.The cloud can help deliver IT as a standardized service…freeing you up to focus on your business
- Slide Objectives:Explain the three established terms in the industry for cloud servicesSpeaker Notes:There is a lot of talk in the industry about different terms like Platform as a Service, Infrastructure as a Service, and Software as a Service.Since PDC08 when we first announced the Windows Azure our focus has been on delivering a platform as a service offering where you can build applications. Where the platform abstracts you from the complexities of building and running applications. We fundamentally believe that the future path forward for development is by providing a platform. In fact, as you’ll see in a few minutes, we believe that there are a number of new capabilities that should be delivered as services to the platform.Notes:There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services.The industry has defined three categories of services:IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another. SaaS offerings needn’t be developed upon PaaS offerings although solutions built on PaaS offerings are often delivered as SaaS. PaaS offerings also needn’t expose IaaS and there’s more to PaaS than just running platforms on IaaS.
- Slide Objectives:Explain the differences and relationship between IaaS, PaaS, and SaaS in more detail.Speaker Notes:Here’s another way to look at the cloud services taxonomy and how this taxonomy maps to the components in an IT infrastructure. Packaged SoftwareWith packaged software a customer would be responsible for managing the entire stack – ranging from the network connectivity to the applications. IaaSWith Infrastructure as a Service, the lower levels of the stack are managed by a vendor. Some of these components can be provided by traditional hosters – in fact most of them have moved to having a virtualized offering. Very few actually provide an OSThe customer is still responsible for managing the OS through the Applications. For the developer, an obvious benefit with IaaS is that it frees the developer from many concerns when provisioning physical or virtual machines. This was one of the earliest and primary use cases for Amazon Web Services Elastic Cloud Compute (EC2). Developers were able to readily provision virtual machines (AMIs) on EC2, develop and test solutions and, often, run the results ‘in production’. The only requirement was a credit card to pay for the services.PaaSWith Platform as a Service, everything from the network connectivity through the runtime is provided and managed by the platform vendor. The Windows Azure best fits in this category today. In fact because we don’t provide access to the underlying virtualization or operating system today, we’re often referred to as not providing IaaS.PaaS offerings further reduce the developer burden by additionally supporting the platform runtime and related application services. With PaaS, the developer can, almost immediately, begin creating the business logic for an application. Potentially, the increases in productivity are considerable and, because the hardware and operational aspects of the cloud platform are also managed by the cloud platform provider, applications can quickly be taken from an idea to reality very quickly.SaaSFinally, with SaaS, a vendor provides the application and abstracts you from all of the underlying components.
- Slide Objectives:Provide a high level summary of Windows Azure and what it enables at a high levelSpeaker Notes:What is Azure?FlexibleWindows Azure is now more flexible then ever beforeWindows Azure helped pioneer the concept of Platform as a ServiceIt provides a rich set of managed services enabling you to compose applications. We’re now making those services richer. We have infrastructure as a service. Including the ability to host and deploy durable virtual machines in the cloud running both Windows and LinuxOpenSome of you maybe surprised to hear Linux at a Microsoft conference.Our support of linux is just one example of how we’re embracing openness in a fundamental new way. With the June release we are supporting more operating systems, more languages, and more open protocolsReleasing all of the Azure SDKs on GitHub under an open source license. SummaryWe believe the end result is truly a unique modelYou can now use both platform as a service and infrastructure as a service *together*You can now use the best of the Microsoft ecosystem and the best of the open source ecosystem *together*Enabling you to build better and more scalable solutions. Notes:Comprehensive set of services that enable you to build, host and scale applications in Microsoft datacenters Windows Azure is an open and flexible cloud platform that enables you to quickly build, deploy and manage applications across a global network of Microsoft-managed datacenters. You can build applications using any language, tool or framework. And you can integrate your public cloud applications with your existing IT environment.
- Speaker Notes:Windows Azure runs on datacenters around the worldEnabling you to deploy and run applications and infrastructure close to your customers. Notes:Windows Azure services such as compute and storage are now available in 8 worldwide datacenters with an additional 24 Content Delivery Network endpoints. You can’t have a real cloud without a data center.
- Speaker Notes:Windows Azure services are backed by a monthly SLAGiving you the confidence to deliver applications and solutions to your customers
- Speaker Notes:With Windows Azure you pay only for what you useEnabling you to avoid up front cost and scale as your business grows.
- Speaker Notes:One of the other things we do with Windows Azure to enable that is provide a bunch of Application Building BlocksThese are managed services that we run that provide a lot of value so you can avoid standing up the infrastructure for common capabilitiesYou always can stand up VMs and put anything you want in itBut in a lot of cases you will find that we have built in services that we deliver or that are delivered by our partnersWhat’s cool is that you can use any of these services with a VM, with a Web Site, or with a Cloud Service – so you have flexibility in how you will consume them.
- Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
- Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
- Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
- Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
- Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
- Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.
- Key points (bullets refer 1:1 to the 6 sentences on the slide).New Office 365 opportunityWith Office 365, a developer can now assume that Exchange, Lync, SharePoint servers are available even for a small business scenarios. That opens the door to creating apps that leverage SharePoint for collaboration, Lync for voice, without worrying about their availability anywhere. Imagine an app for a real-estate lawyer collaborating with a client, with SharePoint serving as the backend for collaboration and Microsoft Word in the front. New Class of Appscontextual apps in office, can understand the content and help you with scenarios such as data mashups with Excel and content augmentation for Word. developers can host their own service that powers apps which makes app updates and new features easy to add, along with a simple in-application app update process [same as wp7, iOS – you have 3 app updates, we’ll do something similar]new model makes building apps that target office and/or SharePoint on mobile devices easy. It also makes writing native apps that target SharePoint easier with client side libraries that match those available on the server.Increased Productivityconsistency is good, it’s a single model across client and server, we’re reducing the API surface area to remove redundancy, and we’re doing things like making API’s between SharePoint and the client side object model identical, this means less time learning and more time coding.javascript is used by 90% of developers today, we want them all writing apps for office and SharePoint, by leveraging standard web technologies in office 15 we’re making it easy for them to use what they know.